These settings are autogenerated from source.
type_json_allow_duplicated_key_with_literal_and_nested_object
When enabled, JSONs like {"a" : 42, "a" : {"b" : 42}} where some key is duplicated but one of them is a nested object are allowed to be parsed.
type_json_skip_duplicated_paths
When enabled, during parsing JSON object into JSON type duplicated paths will be ignored and only the first one will be inserted instead of an exceptio
type_json_skip_invalid_typed_paths
When enabled, fields with values that cannot be coerced to their declared type in JSON type columns with typed paths are skipped instead of throwing an error. Skipped fields are treated as missing and will use default/null values based on the typed path definition.
This setting only applies to JSON type columns (e.g., JSON(a Int64, b String)) where specific paths have declared types. It does not apply to regular JSON input formats like JSONEachRow when inserting into regular typed columns.
Possible values:
- 0 — Disable (throw error on type mismatch).
- 1 — Enable (skip field on type mismatch).
type_json_skip_null_typed_paths
When enabled, typed paths in JSON columns that have NULL values are treated as absent, matching the behavior of dynamic paths. This affects JSON serialization output, introspection functions like JSONAllPaths, JSONHas, JSONExtractRaw, has, and empty/notEmpty checks.
Possible values:
- 0 — Disable (typed paths are always present, even with NULL values).
- 1 — Enable (NULL typed paths are treated as absent).
type_json_use_partial_match_to_skip_paths_by_regexp
When enabled, during parsing JSON object into JSON type regular expressions specified using SKIP REGEXP will require partial match to skip a path. When disabled, full match will be required. Last modified on September 5, 2026
