-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Api v2 improvements #6164
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
+328
−15
Merged
Api v2 improvements #6164
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
2abfadc
API v2: fix returning buckets outside of queried range
RobertJoonas c2214d1
allow time dimensions when querying views_per_visit
RobertJoonas a1d5160
update changelog
RobertJoonas 3d995d3
stop generating bad timeslots instead
RobertJoonas 8f8b3ba
Merge remote-tracking branch 'origin/master' into api-v2-improvements
RobertJoonas 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
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
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.
Instead of re-calculating, can we not access
query.utc_time_rangeinstead?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.
The function itself uses
query.utc_time_rangeunder the hood. The function also evaluatesstartas the latest ofsite.native_stats_start_atandutc_time_range.first.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.
It's not a huge deal, and sort of micro-optimisation, but maybe it would be worth it to ensure
Time.utc_boundariesis called once per query (given of course that none of the used parameters change. Perhaps its result could be stored underquery.computed_utc_time_rangeorquery.effective_utc_time_range?BTW an absolutely out of scope nit but:
could be rewritten as:
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.
Yeah, I guess the main difference between query.utc_time_range and Time.utc_boundaries is that
utc_boundariesis strictly used for native queries, whileutc_time_rangealso defines the range for imported data. So a fitting name would benative_utc_time_range.There's also another difference -- one is
NaiveDateTimeand the other isDateTime.