Database partition mode Part 2 #6409
Open
+1,387
−856
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
…pifhir/hapi-fhir into ja_20240718_pk_schema_selector_merge1
|
Formatting check succeeded! |
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 is the second in a series of PRs to merge in the new database partition mode code.
This PR is preparation for the actual database partitioning:
LongtoJpaPid. For now this change doesn't actually make any functional difference, but it will once we start storing the partition ID in there too.HFJ_RES_VER_PROVtable from theHFJ_RES_VERtable (previously these tables had a@OneToOnerelationship which doesn't really work well with the way we're doing partitioning. This table has been deprecated for one year now, and upgrade instructions are provided for anyone who has older data stored. As a part of this change, all of the optmistic fetches we previously used to fetch this table have been removed.ResourceSearchViewview has been removed in favour of simply loading the HFJ_RES_VER table directly. This does not affect functionality or performance, but will simplify life when we merge in the final partitioning code.