forked from facebookincubator/velox
-
Notifications
You must be signed in to change notification settings - Fork 3
feat: Add support for searching and marshalling the new Timestamp column type. #54
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
Merged
gibber9809
merged 15 commits into
y-scope:presto-0.297-edge-10-clp-connector
from
gibber9809:timestamp-integration-0.297
Mar 2, 2026
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
eacfeaf
Update clp version to pull in faster timestamp marshalling and some b…
gibber9809 96594f3
Add utility for converting nanosecond epoch timestamps to velox times…
gibber9809 a291254
Handle timestamp literal precision special cases for IR and archive s…
gibber9809 ec360b8
Minor syntax fixes.
gibber9809 42ee025
Update existing tests to use timestamp literal in pushdown.
gibber9809 2ba6894
Update out of date query.
gibber9809 2204ef5
Add timestamp filtering and marshalling test for v0.5.0 archives.
gibber9809 4ea87b2
Address comment about test name.
gibber9809 781bbc1
Fix tests.
gibber9809 9066182
Add marshalling code for clp_s::NodeType::Timestamp.
gibber9809 8bb62b3
Lint fix
gibber9809 021d8eb
Fix typo
gibber9809 9215375
Fix typos in tests.
gibber9809 5445fb7
Don't use timestamp() literal in pushdown test 4 for IR, since the ti…
gibber9809 8f673c6
Update test to account for fact that new timestamp format fully prese…
gibber9809 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IR timestamp literal precision mismatch still implies incorrect filtering risk
Line 583-Line 586 documents that IR integer timestamps are microseconds, while
timestamp()literal comparisons assume milliseconds. That is a correctness gap for IR pushdown predicates on microsecond data and can silently mis-filter rows. Please fix the precision normalization path and convert this test to asserttimestamp()behaviour directly instead of relying on a raw integer literal.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arguably the issue is more with the existing test than the pushdown logic. Nominally, timestamps are in millisecond precision for existing kv-ir, though technically this isn't guaranteed.
Medium-term we'll fix for the kv-ir format like we did for the archive format by updating the format to support a timestamp encoding with well-defined precision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gibber9809, thank you for the clarification! That makes sense—documenting the current limitation in the test is reasonable, and having a clear plan to update the kv-ir format with well-defined timestamp precision (similar to the archive format approach) is the right long-term solution. I appreciate you explaining the nominal millisecond precision assumption for existing kv-ir.Looking forward to seeing that format update when you tackle it! 👍
🐰✨
[Taking notes for future reviews...]