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

Partitioning of reports #52

Open
martinthomson opened this issue Oct 31, 2024 · 0 comments
Open

Partitioning of reports #52

martinthomson opened this issue Oct 31, 2024 · 0 comments

Comments

@martinthomson
Copy link
Collaborator

When enforcing anti-replay bounds, or even just in how tasks are constructed, it might be useful for a site to be able to segregate their aggregation tasks into different partitions. This likely results in greatly reduced costs for aggregators, which could be passed on to the sites that use aggregation.

A partitioning key is only useful if both the reports and the aggregation tasks can be bound to a partition. For the reports, we'll need a way to specify that.

@martinthomson martinthomson moved this to Essential in Level 1 API Nov 25, 2024
@martinthomson martinthomson closed this as completed by moving to Nice to have in Level 1 API Nov 25, 2024
@martinthomson martinthomson reopened this Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Nice to have
Development

No branches or pull requests

1 participant