mirror of https://github.com/apache/druid.git
update documentation about multiValueHandling (#14197)
* update documentation about multiValueHandling * Update docs/ingestion/ingestion-spec.md Co-authored-by: Victoria Lim <vtlim@users.noreply.github.com> * Update docs/ingestion/ingestion-spec.md Co-authored-by: Gian Merlino <gianmerlino@gmail.com> * fix spelling --------- Co-authored-by: Victoria Lim <vtlim@users.noreply.github.com> Co-authored-by: Gian Merlino <gianmerlino@gmail.com>
This commit is contained in:
parent
8805d8d7db
commit
152e9375e2
|
@ -226,7 +226,7 @@ Dimension objects can have the following components:
|
||||||
| type | Either `string`, `long`, `float`, `double`, or `json`. | `string` |
|
| type | Either `string`, `long`, `float`, `double`, or `json`. | `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` |
|
| multiValueHandling | For `string` typed dimensions, specifies the type of handling for [multi-value fields](../querying/multi-value-dimensions.md). Possible values are `array` (ingest string arrays as-is), `sorted_array` (sort string arrays during ingestion), and `sorted_set` (sort and de-duplicate string arrays during ingestion). This parameter is ignored for types other than `string`. | `sorted_array` |
|
||||||
|
|
||||||
#### Inclusions and exclusions
|
#### Inclusions and exclusions
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue