Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add documentation re alphabetical sorted of MV dimensions (#10695)

This commit is contained in:
Lasse Krogh Mammen 2021-05-07 09:12:32 +01:00 committed by GitHub
parent d73f72e508
commit 9be2a5cdc2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/ingestion/index.md
View File

@ -479,6 +479,7 @@ Dimension objects can have the following components:
| type | Either `string`, `long`, `float`, or `double`. | `string` | | type | Either `string`, `long`, `float`, or `double`. | `string` |
| name | The name of the dimension. This will be used as the field name to read from input records, as well as the column name stored in generated segments.<br><br>Note that you can use a [`transformSpec`](#transformspec) if you want to rename columns during ingestion time. | none (required) | | name | The name of the dimension. This will be used as the field name to read from input records, as well as the column name stored in generated segments.<br><br>Note that you can use a [`transformSpec`](#transformspec) if you want to rename columns during ingestion time. | none (required) |
| createBitmapIndex | For `string` typed dimensions, whether or not bitmap indexes should be created for the column in generated segments. Creating a bitmap index requires more storage, but speeds up certain kinds of filtering (especially equality and prefix filtering). Only supported for `string` typed dimensions. | `true` | | createBitmapIndex | For `string` typed dimensions, whether or not bitmap indexes should be created for the column in generated segments. Creating a bitmap index requires more storage, but speeds up certain kinds of filtering (especially equality and prefix filtering). Only supported for `string` typed dimensions. | `true` |
| multiValueHandling | Specify the type of handling for [multi-value fields](../querying/multi-value-dimensions.md). Possible values are `sorted_array`, `sorted_set`, and `array`. `sorted_array` and `sorted_set` order the array upon ingestion. `sorted_set` removes duplicates. `array` ingests data as-is | `sorted_array` |
#### Inclusions and exclusions #### Inclusions and exclusions

2
docs/querying/multi-value-dimensions.md
View File

@ -25,7 +25,7 @@ title: "Multi-value dimensions"
Apache Druid supports "multi-value" string dimensions. These are generated when an input field contains an Apache Druid supports "multi-value" string dimensions. These are generated when an input field contains an
array of values instead of a single value (e.g. JSON arrays, or a TSV field containing one or more `listDelimiter` array of values instead of a single value (e.g. JSON arrays, or a TSV field containing one or more `listDelimiter`
characters). characters). By default Druid ingests the values in alphabetical order, see [Dimension Objects](../ingestion/index.md#dimension-objects) for configuration.
This document describes the behavior of groupBy (topN has similar behavior) queries on multi-value dimensions when they This document describes the behavior of groupBy (topN has similar behavior) queries on multi-value dimensions when they
are used as a dimension being grouped by. See the section on multi-value columns in are used as a dimension being grouped by. See the section on multi-value columns in

1
website/.spelling
View File

@ -1880,3 +1880,4 @@ TiB
PiB PiB
protobuf protobuf
Golang Golang
multiValueHandling