-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-index All Registries For All Fields to be Searchable #338
Comments
📆 11/2024 status: Tightly coupled with #230, delayed 1 sprint. No impact on other tasks anticipated. |
#339 nearing completion, #352 outstanding @jordanpadams does the EN fix need to avoid downtime like ATM, or is it fine to have @sjoshi-jpl do the index delete asap and then @tloubrieu-jpl or I load the data when we get to it? |
@alexdunnjpl similar to ATM, it should be a near-real time cutover. it is OK if we have some downtime (e.g. time it takes to load the data), but nothing overly significant. I can also help reload the data, if needed. I think the process is documented on the wiki, so I can try to follow that. |
Both subtasks blocked in the immediate-term, but nothing to do to unblock except wait. |
📆 12/2024 status: Awaiting additional input from AWS. No impact on other tasks. |
@alexdunnjpl to confirm, this is blocked awaiting AWS? |
@jordanpadams negative - I was supposed to re-test on the 7th following their tuning actions, but then all that happened. I'll see if it's easily testable today, otherwise I'll need to wait until the license servers are back online (Monday?) |
@alexdunnjpl copy. thanks for the status |
Status: still blocked by ongoing AWS resolution to #329 |
💡 Description
Right now, we have made numerous updates to harvest to ensure all fields are searchable, however, this does not fix all the data that was loaded before those fixes.
Sub-tasks
The text was updated successfully, but these errors were encountered: