4246 Avoid unnecessary percolator requests during Docket BankruptcyData and Parties ingestion #4262
Conversation
This file contains 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
…ed docket content
- In order to RECAPDocuments percolation can have access to parties.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR solves #4246 by adding a flag to the Docket before it is saved, so the percolation on the docket save signal is skipped.
The flag
skip_percolator_requestis used in processes that merge eitherBankruptcyDataorParties. If we know there areBankruptcyDataorPartiesto be merged in a subsequent step, the percolation on Docketsave()is avoided and is only executed after BankruptcyData or Parties are ingested and indexed into ES.An additional change is related to the merging of parties. I've changed the order in process that merge parties so that hey are merged and indexed before ingesting the Docket entries. This ensures that when the
RECAPDocumentsare percolated upon their creation or update, they have access to the updated Parties data, and alerts involving Parties and RECAPDocuments fields can be matched.Fixes: #4246