V4.0 #58
Merged
V4.0 #58
Conversation
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
added 13 commits
November 14, 2023 11:02
Added more logging in case we cannot find an interval by shorthand. Added getLogger method to retrieve the logger which was set in the DruidClient.
…o accept NULL as value.
- Removed GroupByV1. GroupBy v1 is a legacy engine and has not been supported since 2021. - **Removed extraction functions.** Extraction functions are deprecated in druid and are NOT build in the new NullFilter, EqualityFilter and RangeFilter. These are deprecated and should be replaced by expressions. This is poorly documented, but can be found here: apache/druid#14612 Therefore, we have decided to remove the extraction functionality completely. You can replace the functionality of extraction functions with expressions (and virtual columns). See below for some examples. - Added `RangeFilter` which replaces the `BoundFilter`. See NULL usage sector below. - Added `EqualityFilter` which replaces the `SelectorFilter`. See NULL usage sector below. - `whereBetween` now uses the `range` filter. The `whereBetween` doesn't accept an SortingOrder anymore, but a DataType. - The `whereFlags()` method does not accept `$useJavascript` anymore, as it used an expression filter. - Removed `orWhereNotColumn`. This was a left-over and should have been removed in v3. - Added support for authentication in the druid client.
remenic
reviewed
Mar 19, 2024
remenic
reviewed
Mar 19, 2024
Co-authored-by: Richard Stellingwerff <remenic@gmail.com>
Co-authored-by: Richard Stellingwerff <remenic@gmail.com>
remenic
approved these changes
Mar 19, 2024
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.
are NOT build in the new NullFilter, EqualityFilter and RangeFilter. These are deprecated and
should be replaced by expressions. This is poorly documented, but can be found here:
remove extractionFn from equality, null, and range filters apache/druid#14612
Therefore, we have decided to remove the extraction functionality completely. You can replace the functionality of
extraction functions with expressions (and virtual columns). See below for some examples.
RangeFilterwhich replaces theBoundFilter. See NULL usage sector below.EqualityFilterwhich replaces theSelectorFilter. See NULL usage sector below.whereBetweennow uses therangefilter. ThewhereBetweendoesn't accept an SortingOrder anymore, but a DataType.whereFlags()method does not accept$useJavascriptanymore, as it used an expression filter.orWhereNotColumn. This was a left-over and should have been removed in v3.whereArrayContainsandorWhereArrayContainsfilter methods.