-
Notifications
You must be signed in to change notification settings - Fork 109
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
Inventory uses SOLR 8 #3697
Comments
Inventory is now successfully running with Solr 8 in development space, https://inventory-dev-datagov.app.cloud.gov/dataset/ It is using the Upon relevant review and discussions, we can update Inventory to Solr 8 at any time. |
We're going to hold off on deploying this change until catalog.data.gov is also on cloud.gov and we're less worried disturbing the static deployment of EKS that underpins it. |
We have decided that while catalog has certain blockers, these aren't relevant for inventory. The security and other benefits from using a single stack are worth taking this work on now, instead of staying on solr 6. @nickumia-reisys re-deployed to development workspace, and the system looks great. I tested searching on dataset title, description, email field, and publisher: all worked great. We will need to schedule around @hkdctol various showcases, and will want to deploy to staging manually to verify the re-sync will go fine as the next steps for this ticket. |
Moving to blocked until SOLR8 in the SSB is production ready |
Leaving in blocked for now, pending #3817 |
Historical Issues: |
User Story
In order to [goal], [stakeholder] wants [change].
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
[AND optionally another precondition]
WHEN [a triggering event] happens
THEN [a verifiable outcome]
[AND optionally another verifiable outcome]
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Security Considerations (required)
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
Sketch
[Notes or a checklist reflecting our understanding of the selected approach]
The text was updated successfully, but these errors were encountered: