-
Notifications
You must be signed in to change notification settings - Fork 157
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
Refresh fhir-persistence-schema parameter-names.properties #3563
Comments
steps:
|
for QA just hook up to the database after provisioning and confirm the new parameters exist under parameter_names |
when we looked at this together a while back, I thought I saw |
@PrasannaHegde1 I think we need to redo the exercise of looking for missing parameters. minimal-json.txt includes locally, when I turn tracing up, i see the following message which indicates that it was not included in the list of parameter names that we pre-populate:
I'm not sure why we wouldn't have noticed that one the first time we did this exercise, but I'm worried there might be others like it. |
there are no more known search parameters from the core spec which aren't prepopulated to the db now |
Is your feature request related to a problem? Please describe.
While performing a large reindex, we noticed a few deadlocks and at least one was related to a search parameter that should be in our default (pre-populated) parameter_name table, but isn't:
communication:text
This list was originally created by ingesting a bunch of data with the default config and then grabbing all of the parameter names. However, our search parameter processing has likely evolved since then.
Describe the solution you'd like
Repeat the process for generating parameter_names.properties so that a fresh db will be pre-populated with the most accurate list of built-in parameter names possible.
Describe alternatives you've considered
Acceptance Criteria
AND [another precondition]
WHEN [test step]
AND [test step]
THEN [verification step]
AND [verification step]
Additional context
If we do this before FHIR R4B, we'll need to do it again after that.
The text was updated successfully, but these errors were encountered: