Registry Search + BOR: Move Importer/Re-indexer into GCP, SPIKE
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This ticket is to investigate the following and make tickets accordingly
The importer/reindexer pulls data from COLIN and LEAR and refreshes the solr indexes with it for registry search and for director search.
Will need to look into options for doing this in GCP as we won't be able to connect to COLIN from there. We can probably use the warehouse, but it is a up to a day behind so some alterations to resync aftwerwards would need to be made.
I think we will be able to update the network policy for LEAR, but this also needs investigation.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Investigate how the importer/reindexer reads COLIN and LEAR and refreshes the Solr indexes, then document GCP options, warehouse lag and resync handling, and LEAR network-policy constraints as follow-up tickets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, data-engineering, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100