Skip to content

[Docs] fix typos in tabs and header in the ANSI SQL migration guide #17673

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.

Sign up for GitHub

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
317brian merged 1 commit into from
Jan 28, 2025
Merged

[Docs] fix typos in tabs and header in the ANSI SQL migration guide #17673

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/release-info/migr-ansi-sql-null.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ In Apache Druid 32.0.0, legacy configurations which were incompatible with the A
These configurations were:
* `druid.generic.useDefaultValueForNull`
* `druid.expressions.useStrictBooleans`
* `druid.generic.useThreeValueLogicForNativeFilters` 
* `druid.generic.useThreeValueLogicForNativeFilters`

This guide provides strategies for Druid operators who rely on legacy Druid null handling behavior in their applications to transition to Druid 32.0.0 or later.

Expand All @@ -50,7 +50,7 @@ Prior to Druid 28.0.0, Druid defaulted to a legacy mode which stored default val
In this mode, Druid created segments with the following characteristics at ingestion time:

- String columns couldn't distinguish an empty string, `''`, from null.
Therefore, Druid treated them both as interchangeable values.
Therefore, Druid treated both values as interchangeable.
- Numeric columns couldn't represent null valued rows.
Therefore, Druid stored `0` instead of `null`.

Expand Down Expand Up @@ -207,7 +207,7 @@ The following example shows how to coerce empty strings into null to accommodate

<Tabs>

<TabItem value="0" label="SQL-based batcn">
<TabItem value="0" label="SQL-based batch">

```sql
REPLACE INTO "null_string" OVERWRITE ALL
Expand Down Expand Up @@ -286,7 +286,7 @@ PARTITIONED BY MONTH

Druid ingests the data with no empty strings as follows:

| `__time` | `string_examle` |
| `__time` | `string_example` |
| -- | -- | -- |
| `2024-01-01T00:00:00.000Z`| `my_string`|
| `2024-01-02T00:00:00.000Z`| `null`|
Expand All @@ -305,7 +305,7 @@ If you want to maintain null values in your data within Druid, you can use the f

Consider the following Druid datasource `null_example`:

| `__time` | `string_examle` | `number_example`|
| `__time` | `string_example` | `number_example`|
| -- | -- | -- |
| `2024-01-01T00:00:00.000Z`| `my_string`| 99 |
| `2024-01-02T00:00:00.000Z`| `empty`| 0 |
Expand Down