-
-
Notifications
You must be signed in to change notification settings - Fork 61
fix(search_issues): stop truncating timestamp_ms in search_issues #7373
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
Open
cvxluo
wants to merge
4
commits into
master
Choose a base branch
from
cvxluo/stop-truncating-timestamp_ms-search_issues
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+41
−5
Conversation
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
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In #7362, we populate
timestamp_ms
insearch_issues
by just copying thetimestamp
of the event, since the event timestamp had all the precision we needed. I had assumed that Clickhouse was the one that truncated thetimestamp
to seconds, but it turns out there's also JSONRowEncoder, which forcefully takesdatetime
objects and chops off the milliseconds:snuba/snuba/clickhouse/http.py
Lines 54 to 55 in 799e027
snuba/snuba/clickhouse/__init__.py
Line 1 in 7bfa538
I don't want to change DATETIME_FORMAT, since that would be very impactful to a lot of existing schemas. To work around this, we make
timestamp_ms
an actual timestamp in milliseconds and pass it to clickhouse, which then successfully does the conversion to DateTime64(3), and will populatetimestamp_ms
with timestamps that have the appropriate amount of precision.One alternative I considered was wrapping
timestamp_ms
in a special DateTimeWithMorePrecision class and special-casing it inhttp.py
, but I think that just adds more indirection for this specific feature — if we have more columns that need additional precision that are managed by JSONRowEncoder, I think that would be an appropriate followup.