This is an automated email from the ASF dual-hosted git repository.
victoria pushed a commit to branch 30.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/30.0.0 by this push:
new 3cb37e8414e Docs - Revise removal date for legacy two-value logic and
null handling modes (#16590)
3cb37e8414e is described below
commit 3cb37e8414e5297b2b7110b2b7f7e94cc9f4b4c1
Author: Charles Smith <[email protected]>
AuthorDate: Fri Jun 14 10:37:13 2024 -0700
Docs - Revise removal date for legacy two-value logic and null handling
modes (#16590)
---
docs/querying/sql-data-types.md | 2 +-
docs/release-info/release-notes.md | 3 +--
docs/release-info/upgrade-notes.md | 3 +--
3 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/docs/querying/sql-data-types.md b/docs/querying/sql-data-types.md
index 092e6823250..d06cbe5e8c0 100644
--- a/docs/querying/sql-data-types.md
+++ b/docs/querying/sql-data-types.md
@@ -155,7 +155,7 @@ For examples of null handling, see the [null handling
tutorial](../tutorials/tut
### Legacy null handling mode
:::info
-To ensure Druid always behaves in an ANSI SQL compatible manner, this mode
will be removed in a future release.
+To ensure Druid always behaves in an ANSI SQL compatible manner, we currently
plan to remove this behavior in Druid 32.0.0.
:::
You can set `druid.generic.useDefaultValueForNull = true` to revert to Druid's
deprecated legacy null handling mode, the default for Druid 27.0.0 and prior
releases. This mode is not recommended.
diff --git a/docs/release-info/release-notes.md
b/docs/release-info/release-notes.md
index fb5f922f666..00415c02860 100644
--- a/docs/release-info/release-notes.md
+++ b/docs/release-info/release-notes.md
@@ -57,9 +57,8 @@ For tips about how to write a good release note, see [Release
notes](https://git
As part of the continued improvements to Druid, we are deprecating certain
features and behaviors in favor of newer iterations that offer more robust
features and are more aligned with standard ANSI SQL. Many of these new
features have been the default for new deployments for several releases.
-The following features are deprecated, and we plan to remove support as early
as Druid 36.0.0:
+The following features are deprecated, and we currently plan to remove support
in Druid 32.0.0:
-* **Multi-value dimensions**: Druid now offers support for [array
types](../querying/sql-data-types.md#arrays).
* **Non-SQL compliant null handling**: By default, Druid now differentiates
between an empty string and a record with no data as well as between an empty
numerical record and `0`. For more information, see [NULL
values](../querying/sql-data-types.md#null-values). For a tutorial on the
SQL-compliant logic, see the [Null handling
tutorial](../tutorials/tutorial-sql-null.md).
* **Non-strict Boolean handling**: Druid now strictly uses `1` (true) or `0`
(false). Previously, true and false could be represented either as `true` and
`false` or as `1` and `0`, respectively. In addition, Druid now returns a null
value for Boolean comparisons like `True && NULL`. For more information, see
[Boolean logic](../querying/sql-data-types.md#boolean-logic). For examples of
filters that use the SQL-compliant logic, see [Query
filters](../querying/filters.md).
* **Two-value logic**: By default, Druid now uses three-valued logic for both
ingestion and querying. This primarily affects filters using logical NOT
operations on columns with NULL values. For more information, see [Boolean
logic](../querying/sql-data-types.md#boolean-logic). For examples of filters
that use the SQL-compliant logic, see [Query filters](../querying/filters.md).
diff --git a/docs/release-info/upgrade-notes.md
b/docs/release-info/upgrade-notes.md
index 78d94b15105..8b5052c0db5 100644
--- a/docs/release-info/upgrade-notes.md
+++ b/docs/release-info/upgrade-notes.md
@@ -30,9 +30,8 @@ For the full release notes for a specific version, see the
[releases page](https
As part of the continued improvements to Druid, we are deprecating certain
features and behaviors in favor of newer iterations that offer more robust
features and are more aligned with standard ANSI SQL. Many of these new
features have been the default for new deployments for several releases.
-The following features are deprecated, and we plan to remove support as early
as Druid 36.0.0:
+The following features are deprecated, and we currently plan to remove support
as early as Druid 32.0.0:
-* **Multi-value dimensions**: Druid now offers support for [array
types](../querying/sql-data-types.md#arrays).
* **Non-SQL compliant null handling**: By default, Druid now differentiates
between an empty string and a record with no data as well as between an empty
numerical record and `0`. For more information, see [NULL
values](../querying/sql-data-types.md#null-values). For a tutorial on the
SQL-compliant logic, see the [Null handling
tutorial](../tutorials/tutorial-sql-null.md).
* **Non-strict Boolean handling**: Druid now strictly uses `1` (true) or `0`
(false). Previously, true and false could be represented either as `true` and
`false` or as `1` and `0`, respectively. In addition, Druid now returns a null
value for Boolean comparisons like `True && NULL`. For more information, see
[Boolean logic](../querying/sql-data-types.md#boolean-logic). For examples of
filters that use the SQL-compliant logic, see [Query
filters](../querying/filters.md).
* **Two-value logic**: By default, Druid now uses three-valued logic for both
ingestion and querying. This primarily affects filters using logical NOT
operations on columns with NULL values. For more information, see [Boolean
logic](../querying/sql-data-types.md#boolean-logic). For examples of filters
that use the SQL-compliant logic, see [Query filters](../querying/filters.md).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
