Skip to content

feat: Refine timestamp from search after#72

Open
Darkheir wants to merge 1 commit into
sekoiafrom
feat/refine_timestamp_search_after
Open

feat: Refine timestamp from search after#72
Darkheir wants to merge 1 commit into
sekoiafrom
feat/refine_timestamp_search_after

Conversation

@Darkheir

Copy link
Copy Markdown
Collaborator

Description

Describe the proposed changes made in this PR.

How was this PR tested?

Describe how you tested this PR.

Copilot AI review requested due to automatic review settings June 25, 2026 12:36

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refines the effective start_timestamp/end_timestamp bounds used during split selection by additionally tightening them from the search_after cursor when the primary sort field is the timestamp field, aiming to improve pruning for paginated searches.

Changes:

  • Import SortOrder and add refine_timestamps_from_search_after to derive tighter timestamp bounds from search_after.
  • Invoke the refinement during refine_and_list_matches after AST-based timestamp extraction and after datetime cursor normalization.
  • Add unit tests covering DESC/ASC behavior and no-op scenarios.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread quickwit/quickwit-search/src/root.rs Outdated
Comment thread quickwit/quickwit-search/src/root.rs
Comment thread quickwit/quickwit-search/src/root.rs
@Darkheir Darkheir force-pushed the feat/refine_timestamp_search_after branch from 7fb4fa5 to a703f12 Compare June 25, 2026 12:51
Signed-off-by: Darkheir <raphael.cohen@sekoia.io>
@Darkheir Darkheir force-pushed the feat/refine_timestamp_search_after branch from a703f12 to 3a37992 Compare June 25, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants