-
Notifications
You must be signed in to change notification settings - Fork 4
Implement FHIR Async Request Pattern for Direct Broker using CQL #539
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
Implement FHIR Async Request Pattern for Direct Broker using CQL #539
Conversation
d4ec6b4
to
4890e23
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #539 +/- ##
=============================================
+ Coverage 79.29% 80.05% +0.76%
- Complexity 690 727 +37
=============================================
Files 163 166 +3
Lines 2932 3044 +112
Branches 291 299 +8
=============================================
+ Hits 2325 2437 +112
Misses 487 487
Partials 120 120 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
src/main/java/de/numcodex/feasibility_gui_backend/query/broker/direct/AsyncRequestExecutor.java
Fixed
Show resolved
Hide resolved
4890e23
to
233cb5e
Compare
src/test/java/de/numcodex/feasibility_gui_backend/query/broker/direct/DirectSpringConfigIT.java
Fixed
Show fixed
Hide fixed
0f4a8ad
to
b685c05
Compare
Added configuration property `broker.direct.cql.useAsyncRequestPattern` with default value true to support asynchronous request handling when the Direct Broker is using CQL queries. This enhancement improves performance by allowing non-blocking request processing, particularly useful for complex or long-running CQL queries. The change is part of the broker client configuration and can be controlled via the environment variable `BROKER_CLIENT_DIRECT_CQL_USE_ASYNC_REQUEST_PATTERN` when needed.
Increase time interval to test timeout against.
b685c05
to
f84866e
Compare
@@ -88,6 +88,8 @@ app: | |||
secret: ${BROKER_CLIENT_DIRECT_AUTH_OAUTH_CLIENT_SECRET:} | |||
enabled: ${BROKER_CLIENT_DIRECT_ENABLED:false} | |||
useCql: ${BROKER_CLIENT_DIRECT_USE_CQL:false} | |||
cql: | |||
useAsyncRequestPattern: ${BROKER_CLIENT_DIRECT_CQL_USE_ASYNC:false} |
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.
I'll probably move this parameter to another place in a separate issue/pr
Added configuration property
broker.direct.cql.useAsyncRequestPattern
with default value false to support asynchronous request handling when the Direct Broker is using CQL queries. This enhancement improves performance by allowing non-blocking request processing, particularly useful for complex or long-running CQL queries.The change is part of the broker client configuration and can be controlled via the environment variable
BROKER_CLIENT_DIRECT_CQL_USE_ASYNC_REQUEST_PATTERN
when needed and defaults tofalse
for staying compatible with deployments using HAPI based CQL-enabled FHIR servers which reject requests with unknown headers.