From 8085ee7217d90e0e3f133985a52ec2e0b0552992 Mon Sep 17 00:00:00 2001 From: Jill Osborne Date: Mon, 28 Nov 2022 11:22:06 +0000 Subject: [PATCH] Update nested-columns.md --- docs/querying/nested-columns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/querying/nested-columns.md b/docs/querying/nested-columns.md index ccc33b141cd..77af91ddff8 100644 --- a/docs/querying/nested-columns.md +++ b/docs/querying/nested-columns.md @@ -326,7 +326,7 @@ PARTITIONED BY ALL ## Ingest a JSON string as COMPLEX -If your source data uses a string representation of your JSON column, you can still ingest the data as `COMPLEX` as follows: +If your source data contains serialized JSON strings, you can ingest the data as `COMPLEX` as follows: - During native batch ingestion, call the `parse_json` function in a `transform` object in the `transformSpec`. - During SQL-based ingestion, use the PARSE_JSON keyword within your SELECT statement to transform the string values to JSON. - If you are concerned that your data may not contain valid JSON, you can use `try_parse_json` for native batch or `TRY_PARSE_JSON` for SQL-based ingestion. For cases where the column does not contain valid JSON, Druid inserts a null value.