-
Notifications
You must be signed in to change notification settings - Fork 24
Fix pseudo-irregular time series direct reads #1781
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
krowvin
wants to merge
11
commits into
develop
Choose a base branch
from
issue-1745-pseudo-irregular
base: develop
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.
+140
−59
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
97062d8
Fix pseudo-irregular time series direct reads
krowvin 2260736
Fix pseudo-irregular direct time-series reads
krowvin eeca34f
Merge branch 'develop' into issue-1745-pseudo-irregular
krowvin 5ef0b0c
Restore direct-read unit validation
krowvin 48b5d94
Merge branch 'develop' into issue-1745-pseudo-irregular
krowvin 744e065
Merge develop into issue-1745-pseudo-irregular
krowvin 631dc01
Align direct TSV date predicates with retrieve_ts
krowvin cea2f38
Simplify direct read regularity handling
krowvin 530030f
Fix direct read unit and version filters
krowvin e545df4
Remove direct TSV physical date filters
krowvin 840b53d
Trust database LRTS regularity
krowvin 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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
why are we spending time formatting a timestamp that can be used as-is in the query?
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.
When I was trying to run the test for TimeSeriesDirectReadParityIT it started failing/saying missing.
I agree converting from one and back to the other is wasted cycles though. Any ideas on how to make it so it'll match up with
AV_TSV_DQU.DATE_TIME?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.
Hmm. that's, unexpected, especially since it's a begin/end time stamp so a few seconds on either side shouldn't matter much. Might have something to do with the columns being
Dateinstead ofTimestampin the database.Presumably the performance is still improved overall? If so, I'd argue that challenge is reasonable cause to leave the extra conversions in. Not like it happens for every row. Just put a comment in about why for future readers.