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.

Sign up for GitHub

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

Jump to bottom

Cap query end date in certain cases, responsibly #839

Open
apmoriarty opened this issue Jun 23, 2020 · 1 comment · May be fixed by NationalSecurityAgency/datawave-metadata-utils#4
Open

Cap query end date in certain cases, responsibly #839

apmoriarty opened this issue Jun 23, 2020 · 1 comment · May be fixed by NationalSecurityAgency/datawave-metadata-utils#4

Comments

@apmoriarty
Copy link
Collaborator

It's possible to specify a date range that exceeds the limit for data stored. A specific example may be seen in RangeStream.createFullFieldIndexScanList().

It should be possible to scan the metadata table to determine the most recent shards and then limit the query end date based on that.
@ivakegg
Copy link
Collaborator

ivakegg commented Jun 23, 2020

The 'f' (frequency) metadata could be used to determine what days we actually have data for.

@rcarterjr rcarterjr linked a pull request Sep 9, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Work in Progress helper function getEndDateCap rcarterjr/datawave-metadata-utils
2 participants
@ivakegg @apmoriarty