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

Feature/composite timestamp #2187

Open
wants to merge 14 commits into
base: integration
Choose a base branch
from
Open

Conversation

hlgp
Copy link
Collaborator

@hlgp hlgp commented Dec 8, 2023

No description provided.

@hlgp hlgp changed the title WIP: Feature/composite timestamp Feature/composite timestamp Jan 29, 2024
ivakegg and others added 4 commits February 9, 2024 11:36
* Refined the composite timestamp to check for bounds
Added a few tests as such

* Allow negative event dates

* More tests

* add more tests

* formatter

---------

Co-authored-by: hlgp <hlgp@users.noreply.github.com>
* Add get and set Timestamp on the record container.
* Override getDate to be compatible with extending classes
* Updated sharded ingest to appropriately use getTimestamp vs getDate
* Updated index table to use composite timestamp
* Added an explicit INVALID_TIMESTAMP instead of using Long.MIN_VALUE to determine if the date is not set
* Updated the global index uid aggregator to not aggregate across different timestamps
* Removed the "timestampIgnored" flag on the global index uid aggregator as we never turn that off and we don't want to
* Added test to ensure that keys with different timestamps do not get aggregated
…tween

the start-of-day values for the event and age off dates.
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.

None yet

2 participants