-
Notifications
You must be signed in to change notification settings - Fork 120
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 query restriction pushdown for Id #1220
Labels
Comments
Note that it's the DataRequirementsProcessor that does these types of optimizations as a post-processing step. There is some date range pushdown in the translator directly, but it's not as sophisticated as what the DataRequirementsProcessor is doing, and should be deprecated in favor of the DataRequirementsProcessor, IMHO. |
Just to clarify, are you saying that we should always do pushdown as post-processing? Including for Ids? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CQL engine currently supports certain types of query restriction pushdowns, specifically for date filters. In other words, given the following CQL:
the CQL compiler can emit an ELM Retrieve that has that date filter captured in the
datePath
anddateLow
elements.Ideally, we could support the same type of push-downs for
Retrieve
s by id. In other words, these two statements ought to be equivalent with respect to the ELM that's generated:And the ELM that's generated for the
Retrieve
ought to have both theid
and theidProperty
populated in both cases.Acceptance Criteria:
The text was updated successfully, but these errors were encountered: