Skip to content
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

Open
jordanpadams opened this issue Nov 11, 2024 · 9 comments
Open

Re-index All Registries For All Fields to be Searchable #338

jordanpadams opened this issue Nov 11, 2024 · 9 comments

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Nov 11, 2024

💡 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

@jordanpadams
Copy link
Member Author

📆 11/2024 status: Tightly coupled with #230, delayed 1 sprint. No impact on other tasks anticipated.

@alexdunnjpl
Copy link
Contributor

#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?

@jordanpadams
Copy link
Member Author

@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.

@jordanpadams jordanpadams moved this from Sprint Backlog to In Progress in B15.1 Dec 10, 2024
@alexdunnjpl
Copy link
Contributor

Both subtasks blocked in the immediate-term, but nothing to do to unblock except wait.

@jordanpadams
Copy link
Member Author

📆 12/2024 status: Awaiting additional input from AWS. No impact on other tasks.

@jordanpadams jordanpadams moved this from In Progress to Blocked in B15.1 Jan 9, 2025
@jordanpadams
Copy link
Member Author

@alexdunnjpl to confirm, this is blocked awaiting AWS?

@alexdunnjpl
Copy link
Contributor

alexdunnjpl commented Jan 9, 2025

@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?)

@jordanpadams
Copy link
Member Author

@alexdunnjpl copy. thanks for the status

@alexdunnjpl
Copy link
Contributor

Status: still blocked by ongoing AWS resolution to #329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked
Development

No branches or pull requests

2 participants