Skip to content
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

Relay - Distribution Query results handling #5

Open
2 of 7 tasks
beforan opened this issue Nov 19, 2024 · 0 comments
Open
2 of 7 tasks

Relay - Distribution Query results handling #5

beforan opened this issue Nov 19, 2024 · 0 comments
Milestone

Comments

@beforan
Copy link
Member

beforan commented Nov 19, 2024

Is this the right issue type?

  • Yes, I'm planning work for this project team.

Summary

Due to our limited ability to test distribution queries so far, I think there are pieces of this functionality we've overlooked.

Currently Relay performs results aggregation and obfuscation on the Count property of results submitted by sub nodes. This works well for Availability queries.

With other types of analyses (here focusing on Distribution) a results file is submitted, with many rows and counts.

  • Relay will definitely need to aggregate the row counts in these files for correct distribution representation.

  • Relay may need to apply obfuscation to individual row values

Acceptance Criteria

  • Distribution queries are handled successfully end to end
  • Results files submitted for Distribution Queries are correctly aggregated for more than one downstream sub node.
  • Results files submitted for Distribution Queries are correctly obfuscated by Relay
  • Tests pass.
  • Documentation added.

Confirm creation

  • This issue is ready
@beforan beforan transferred this issue from Health-Informatics-UoN/hutch-cohort-discovery Jan 24, 2025
@AndyRae AndyRae added this to the Relay v1.0.0 milestone Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: MoreInfo
Development

No branches or pull requests

2 participants