apache · vtlim · Sep 6, 2022 · Aug 23, 2022 · Aug 23, 2022 · Aug 23, 2022
diff --git a/docs/assets/nested-combined-json.png b/docs/assets/nested-combined-json.png
diff --git a/docs/assets/nested-display-data-types.png b/docs/assets/nested-display-data-types.png
diff --git a/docs/assets/nested-examine-schema.png b/docs/assets/nested-examine-schema.png
diff --git a/docs/assets/nested-extract-as-type.png b/docs/assets/nested-extract-as-type.png
diff --git a/docs/assets/nested-extract-elements.png b/docs/assets/nested-extract-elements.png
diff --git a/docs/assets/nested-group-aggregate.png b/docs/assets/nested-group-aggregate.png
diff --git a/docs/assets/nested-msq-ingestion-transform.png b/docs/assets/nested-msq-ingestion-transform.png
diff --git a/docs/assets/nested-msq-ingestion.png b/docs/assets/nested-msq-ingestion.png
diff --git a/docs/assets/nested-parse-deserialize.png b/docs/assets/nested-parse-deserialize.png
diff --git a/docs/assets/nested-retrieve-json.png b/docs/assets/nested-retrieve-json.png
diff --git a/docs/assets/nested-return-json.png b/docs/assets/nested-return-json.png
diff --git a/docs/ingestion/data-formats.md b/docs/ingestion/data-formats.md
@@ -582,7 +582,9 @@ For example:
 
 ### FlattenSpec
 
-The `flattenSpec` object bridges the gap between potentially nested input data, such as JSON or Avro, and Druid's flat data model. It is an object within the `inputFormat` object.
+The `flattenSpec` object bridges the gap between potentially nested input data, such as Avro or ORC, and Druid's flat data model. It is an object within the `inputFormat` object.
+
+> If you have nested JSON data, you can ingest and store JSON in an Apache Druid column as a `COMPLEX<json>` data type. See [Nested columns](../querying/nested-columns.md) for more information.
 
 Configure your `flattenSpec` as follows:
 

diff --git a/docs/ingestion/ingestion-spec.md b/docs/ingestion/ingestion-spec.md
@@ -223,7 +223,7 @@ Dimension objects can have the following components:
 
 | Field | Description | Default |
 |-------|-------------|---------|
-| type | Either `string`, `long`, `float`, or `double`. | `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) |
 | 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` |

diff --git a/docs/ingestion/schema-design.md b/docs/ingestion/schema-design.md
@@ -201,8 +201,9 @@ like `MILLIS_TO_TIMESTAMP`, `TIME_FLOOR`, and others. If you're using native Dru
 
 ### Nested dimensions
 
-At the time of this writing, Druid does not support nested dimensions. Nested dimensions need to be flattened. For example,
-if you have data of the following form:
+You can ingest and store nested JSON in a Druid column as a `COMPLEX<json>` data type. See [Nested columns](../querying/nested-columns.md) for more information.
+
+If you want to ingest nested data in a format other than JSON&mdash;for example Avro, ORC, and Parquet&mdash;you  must use the `flattenSpec` object to flatten it. For example, if you have data of the following form:
 
 ```
 {"foo":{"bar": 3}}
@@ -214,8 +215,7 @@ then before indexing it, you should transform it to:
 {"foo_bar": 3}
 ```
 
-Druid is capable of flattening JSON, Avro, or Parquet input data.
-Please read about [`flattenSpec`](./ingestion-spec.md#flattenspec) for more details.
+See the [`flattenSpec`](./ingestion-spec.md#flattenspec) documentation for more details.
 
 <a name="counting"></a>
 

diff --git a/docs/misc/math-expr.md b/docs/misc/math-expr.md
@@ -252,7 +252,7 @@ Druid supports a small, simplified subset of the [JSONPath syntax](https://githu
 |`['<name>']`| Child element in bracket notation. |
 |`[<number>]`| Array index. |
 
-See [SQL JSON documentation](../querying/sql-json-functions.md#jsonpath-syntax) for examples.
+See [SQL JSON documentation](../querying/sql-json-functions.md#jsonpath-syntax) for examples and [Nested columns](../querying/nested-columns.md) for more information on ingesting and storing nested data.
 
 ## Reduction functions