Skip to content
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

Update the search configuration to reflect new config and reindex #1730

Merged
merged 4 commits into from
Nov 27, 2020

Conversation

lmsurpre
Copy link
Member

@lmsurpre lmsurpre commented Nov 19, 2020

Update the docs to reflect that fhirServer/searchParameterFilter has been replaced with fhirServer/resources/<resourceType>/searchParameters.

We should probably add more documentation to explain fhirServer/resources/<resourceType>/searchIncludes, fhirServer/resources/<resourceType>/searchRevIncludes, and fhirServer/resources/<resourceType>/searchParameterCombinations,
but for now I just wanted to make sure the stale content was cleaned up.

I also added a section on using the new $reindex operation.

Note that, rather than update them, I removed some examples and the description of the algorithm to reduce the burden of maintenance.

Review suggestion:
rather than viewing the diff, I think its easier to just read the new content at https://github.com/IBM/FHIR/blob/357cdcfc00f6614b1addc3ab32146b71e0202dbd/docs/src/pages/guides/FHIRSearchConfiguration.md

Signed-off-by: Lee Surprenant lmsurpre@us.ibm.com

Update the docs to reflect that `fhirServer/searchParameterFilter` has been replaced with `fhirServer/resources/<resourceType>/searchParameters`.

We should probably add more documentation to explain `fhirServer/resources/<resourceType>/searchIncludes`, `fhirServer/resources/<resourceType>/searchRevIncludes`, and `fhirServer/resources/<resourceType>/searchParameterCombinations`,
but for now I just wanted to make sure the stale content was cleaned up.

I also added a section on using the new `$reindex` operation.

Note that, rather than update them, I removed some examples and the description of the algorithm to reduce the burden of maintenance.

Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
-jar "${JAR}" \
--db-type postgresql \
--fhir-properties fhir.properties \
--tenant-name "YOUR-TENANT-NAME" \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is tenant-name actually used with postgres?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it is, but I copied these argument right from what @punktilious put in our 4.5.0 release notes. I know we have #1640 for cleaning up the arguments needed by this utility, so hopefully we can clean up this doc as part of that.

Copy link
Contributor

@prb112 prb112 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@prb112
Copy link
Contributor

prb112 commented Nov 19, 2020

Left minor comments

Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>

Co-authored-by: Paul Bastide <pbastide@us.ibm.com>
}
},
"Patient": {
Copy link
Contributor

@tbieste tbieste Nov 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest having on of these resource types have "*": "*" for example.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since leaving out searchParameters entirely is equivalent to having a single entry with "*": "*", I don't think it should be common to need "*": "*".
I do cover the scenario where "*": "*" is useful below (line 147).

Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
@lmsurpre lmsurpre merged commit 3480e28 into master Nov 27, 2020
@lmsurpre lmsurpre deleted the lmsurpre-patch-1 branch November 27, 2020 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants