-
Notifications
You must be signed in to change notification settings - Fork 1k
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
History count fix #739
base: master
Are you sure you want to change the base?
History count fix #739
Conversation
Changed history_count_mode ENUM setup
@@ -71,6 +71,7 @@ public class AppProperties { | |||
private List<String> supported_resource_types = new ArrayList<>(); | |||
private List<Bundle.BundleType> allowed_bundle_types = null; | |||
private Boolean narrative_enabled = true; | |||
private String history_count_mode = "CACHED_ONLY_WITHOUT_OFFSET"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be bound to HistoryCountModeEnum like in
hapi-fhir-jpaserver-starter/src/main/java/ca/uhn/fhir/jpa/starter/AppProperties.java
Line 67 in e2d2ea7
private EncodingEnum default_encoding = EncodingEnum.JSON; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The binding to the enum should be strongly typed which would influence this entire PR
Reopening this old PR after addressing changes #500
Resolves this issue #433
During integration testing, it is useful to make rapid search history queries, but unless this flag can be configured we are forced to use the default of waiting 1 minute for the history cache to clear. Instead, during integration test we should always be getting the actual data from the db.