Fix subscription query maximum number of results #678
Merged
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
…d fhir criteria validation before create/update, added dstu2 configurations
… validate-subscription-criteria
javajeff
changed the title
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.
Contains a critical fix for rest hook subscriptions. It currently only searches the default max number of results which is 10. This occurs in two locations:
We need to set the limit higher, in this case 10000, but a higher number can be used.
Contains an enhancement to validate the subscription criteria before performing an update or delete. This will prevent the FHIR server from making subscription queries it cannot parse. If there is an error in the criteria, a bad input return code is returned before the server saves a subscription.
Also removed some unneeded web.xml file templates.