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

Add FederatedQueryPlanner #2216

Merged
merged 75 commits into from
Sep 9, 2024
Merged

Add FederatedQueryPlanner #2216

merged 75 commits into from
Sep 9, 2024

Conversation

lbschanno
Copy link
Collaborator

@lbschanno lbschanno commented Jan 12, 2024

Adds a FederatedQueryPlanner that will break up a query into multiple queries scanning over subsets of the original target date range if field index holes are identified to be present for the query in the target date range.

Note: the work in this PR is dependent on the work in:

Closes #825

lbschanno and others added 9 commits September 19, 2023 04:57
Modify the generation of 'i' (indexed rows) and 'ri' (reverse indexed
rows) in the metadata table such that the column qualifier contains the
event date. This is required as a first step to support efforts for
issue #825 so that we can identify dates when an event was ingested and
included in a frequency count for an associated 'f' row, but was not
indexed.
@lbschanno lbschanno changed the title Task/federated query planner Add FederatedQueryPlanner Jan 13, 2024
ivakegg
ivakegg previously approved these changes Jul 8, 2024
hlgp
hlgp previously approved these changes Aug 27, 2024
@ivakegg ivakegg added the linked label Sep 5, 2024
@hgklohr hgklohr merged commit 04336c4 into integration Sep 9, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle the cases were a field is both indexed and not indexed within a time range
5 participants