-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Allow EARLIEST/EARLIEST_BY/LATEST/LATEST_BY for STRING columns without specifying maxStringBytes #14848
Merged
Merged
Allow EARLIEST/EARLIEST_BY/LATEST/LATEST_BY for STRING columns without specifying maxStringBytes #14848
Changes from 14 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
1444487
PR#8815 added some check that negative values are not accepted; howev…
kgyrtkirk 110d8c0
accept any for earliest/latest
kgyrtkirk 90d10db
extend test
kgyrtkirk 33b8129
fix test
kgyrtkirk 905508d
cleanup test; fix checkstyle
kgyrtkirk 1efcb64
more specific test name
kgyrtkirk 83402e5
accept removal of cast from plan
kgyrtkirk cf3ed18
update test; update docs
kgyrtkirk d0f5487
extend test; disable vectorization - no support for earliest
kgyrtkirk 3b7eaf9
add test for ANY
kgyrtkirk ee73a8b
update docs
kgyrtkirk e41893a
fix br
kgyrtkirk b75be8e
remove ws
kgyrtkirk 11c0fd8
Merge remote-tracking branch 'apache/master' into latest-by-error
kgyrtkirk 8f2691a
merge
kgyrtkirk 9908504
rename maxBytesPerString to maxBytesPerValue
kgyrtkirk 531328c
update docs/querying/sql-functions.md
kgyrtkirk 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 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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -128,7 +128,7 @@ public Aggregation toDruidAggregation( | |
rexNodes.get(1) | ||
), | ||
outputType, | ||
-1 | ||
null | ||
); | ||
break; | ||
case 3: | ||
|
This file contains 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
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.
nit: even though this is only for strings right now, i wonder if we should future-proof this a bit by calling
maxBytesPerString
something likemaxBytesPerValue
insteadThere 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.
I was thinking to also replace
maxBytesPerString
everywhere in the main codebase - but it seems like thismaxBytesPerString
may also appear in thenative
api...so decided against that:https://druid.apache.org/docs/latest/querying/aggregations/
I believe a change like that may cause some troubles - so I wonder which path should we take:
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.
i think leaving them alone is best since in that case it is actually specific to the native stringFirst/stringLast aggregators so its fine that the json properties of that spec are string specific.