SIMSBIOHUB-883: Parse Feature Content into Search Tables#341
Merged
Conversation
|
OpenShift URLs for the PR Deployment:
|
dwhogan
changed the title
|
OpenShift URLs for the PR Deployment:
|
dylanrogowsky-oxd
force-pushed
the
dev
branch
from
3d3b72d to
97e5dc7
Compare
mauberti-bc
reviewed
Feb 26, 2026
Collaborator
|
My same comment form #340 about re-using the database connection between jobs, but it's non-blocking; more food for thought. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Links to Jira Tickets
Description of Changes
As a BioHub background worker, I want submission features to be automatically indexed into the search tables after validation completes, so that new submissions become searchable without manual admin intervention.
Acceptance Criteria
Publishing the Indexing Job
WHEN the
process-submission-featuresjob handler completes validation successfully,THEN a new
index-submission-featuresjob should be published with thesubmissionId,AND the job should follow existing patterns (singleton key, retry config, DLQ).
Processing the Indexing Job
WHEN the
index-submission-featuresjob is picked up by the worker,THEN
SearchFeatureService.indexFeaturesBySubmissionId()should be called,AND features should be inserted into
search_string,search_number,search_datetime, andsearch_spatialtables.Handling Indexing Failures
WHEN the indexing job fails after all retries are exhausted,
THEN the dead letter queue handler should log the failure with error details,
AND the validation job's success should NOT be affected (indexing failure is independent).
Testing Notes