CCD-7841: combines 4262-4769, ccd 6395, ccd 4311#2917
Open
patelila wants to merge 75 commits into
Open
Conversation
* CCD-4775 Modify db trigger to insert the case id's into new table
… and added to V20240619_4790__CCD-4790_Drop_marked_by_logstash_field_case_data.sql
…rCaseworker in FT scenarios
…e when updating case_data.
…o CCD-4769-Create-Index-Table
…nstraint DETAIL: Table "xxx" references "tableA". HINT: Truncate table "xxx" at the same time, or use TRUNCATE ... CASCADE
…IdDoesNotExist() org.opentest4j.AssertionFailedError: Expected org.springframework.dao.DataIntegrityViolationException to be thrown, but nothing was thrown.
…eFailsIfCaseIdDoesNotExist() as Class CaseLinkRepositoryTest runs in Intellij but when all Tests are run these two functions fail.
…' into CCD-4262-4769-Create-Index-Table
…eption at HikariPool.java:596 error
…eption at HikariPool.java:596 error
* To try to fix CallbackInvokerWireMockTest > shouldRetryOnErrorWithIgnoreWarningFalseAndDefaultRetryContext FAILED uk.gov.hmcts.ccd.endpoint.exceptions.CallbackException at CallbackInvokerWireMockTest.java:83 CaseLinkRepositoryTest > testSaveFailsIfCaseIdDoesNotExis() FAILED org.opentest4j.AssertionFailedError at CaseLinkRepositoryTest.java:128 CaseLinkRepositoryTest > testSaveFailsIfLinkedCaseIdDoesNotExist() FAILED org.opentest4j.AssertionFailedError at CaseLinkRepositoryTest.java:140 * Added @DirtiesContext to all Unit tests in the @RunWith(SpringRunner.class) Suite.
…e legacy marked_by_logstash constraint for case pointers and update the Logstash queue trigger to skip pointer rows directly. Revert the test fixture workaround that marked pointer-like rows as already processed, and update the pointer repository test to assert queue behaviour.
…e_data_logstash_queue id as the Elasticsearch external version so queued supplementary-data-only updates are not rejected when case_data.version has not changed.Keep the case version in the indexed document source unchanged.
… the case_data_logstash_queue id as the Elasticsearch external version so queued supplementary-data-only updates are not rejected when case_data.version has not changed.Keep the case version in the indexed document source unchanged." This reverts commit 6ef1900.
… CCD-7841_4262-4769_ccd_6395_ccd_4311
This was referenced Jul 3, 2026
Use case_data.version as the Elasticsearch external version for Logstash writes. This restores CCD-6024 concurrency behaviour so stale case versions are rejected by Elasticsearch instead of silently overwriting newer documents. Note: focused Gradle test did not run due dependency SSL/cert resolution failure, not test failure.
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
6 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.
Before creating a pull request make sure that:
keep-helmlabel has been added, if the helm release should be persisted after a successful buildPlease remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")