Skip to content

Commit 05a79a5

Browse files
authored
Merge pull request #4458 from ClickHouse/Blargian-patch-947791
Update a link
2 parents d7196a4 + 46622c2 commit 05a79a5

File tree

1 file changed

+1
-1
lines changed
  • docs/integrations/data-ingestion/data-formats/json

1 file changed

+1
-1
lines changed

docs/integrations/data-ingestion/data-formats/json/other.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ SELECT JSONExtractString(tags, 'holidays') AS holidays FROM people
7070
1 row in set. Elapsed: 0.002 sec.
7171
```
7272

73-
Notice how the functions require both a reference to the `String` column `tags` and a path in the JSON to extract. Nested paths require functions to be nested e.g. `JSONExtractUInt(JSONExtractString(tags, 'car'), 'year')` which extracts the column `tags.car.year`. The extraction of nested paths can be simplified through the functions [`JSON_QUERY`](/sql-reference/functions/json-functions#JSON_QUERY) and [`JSON_VALUE`](/sql-reference/functions/json-functions#json_value).
73+
Notice how the functions require both a reference to the `String` column `tags` and a path in the JSON to extract. Nested paths require functions to be nested e.g. `JSONExtractUInt(JSONExtractString(tags, 'car'), 'year')` which extracts the column `tags.car.year`. The extraction of nested paths can be simplified through the functions [`JSON_QUERY`](/sql-reference/functions/json-functions#JSON_QUERY) and [`JSON_VALUE`](/sql-reference/functions/json-functions#JSON_VALUE).
7474

7575
Consider the extreme case with the `arxiv` dataset where we consider the entire body to be a `String`.
7676

0 commit comments

Comments
 (0)