dataforgoodfr / dataforgoodfr/12_bloom
[DB] Discussion sur le plan
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 10
- Avg merge
- 1m
- Merged PRs (30d)
- 9
Description
La taille de la DB actuelle est relativement élevée (dbt : 64 GB, spire : 19 GB, old_trawlwatch : 24 GB)
Les tables les plus lourdes sont spire_ais_data, stg_vessel_positionset itm_vessel_positions.
2 propositions :
- hébergée la DB sur serveur local (sauf marts) : problème sécurité ?
- archivage des 3 tables : streaming de spire_ais_data depuis un S3 avec sauvegarde des données collectées pendant l'init.
=> contacter CC pour demander conseil
=> étude d'impact à effectuer
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the sizes of dbt, spire, and old_trawlwatch and the three largest tables: spire_ais_data, stg_vessel_positions, and itm_vessel_positions. Compare the local-server and S3 archival proposals, assess their security and initialization impact, and seek CC's advice; done means an impact study with a recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100