-
Notifications
You must be signed in to change notification settings - Fork 1
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
$cascade operation round 2, incl. recursion #1122
Comments
…chy (default true) and cascade mappings option (default true)
…level | limiting results and swagger parameters
@paynejd This is deployed on QA |
This query returns 211 resources: These two queries (just including/excluding the same map types) should return a total of 212 resources, right? (Because both are going to include the original concept) But the first one is 173 and the second one is 4, for a total of 177 resources.
What is causing the mismatch? |
@snyaggarwal walked us thru an analysis of cascade recursion that showed that the results above were actually correct. See the image below-- we'll want to add a similar diagram to our documentation. Closing this out and further work will take place in #1131 |
Following up on #1088, the next round of work on the $cascade operator will support recursion and hierarchy, and will improve alignment with FHIR.
cascadeHierarchy=true|false
parametercascadeMappings=true|false
includeMappings=false
excludeMapTypes=SAME-AS
-- note that this parameter should be ignored ifmapTypes
parameter is presentcascadeLevels=0
is the current behavior of no recursion;cascadeLevels=1
goes to the next level;cascadeLevels=all
or*
means do all levels and should be the default behaviorThe text was updated successfully, but these errors were encountered: