> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# format_* format settings

> ClickHouse format settings in the format_* generated group.

export const SettingsInfoBlock = ({type, default_value, changeable_without_restart}) => {
  return <div className="not-prose" style={{
    display: "flex",
    flexWrap: "wrap",
    alignItems: "baseline",
    columnGap: "0.5rem",
    rowGap: "0.125rem",
    margin: "0.375rem 0",
    fontSize: "0.8125rem",
    lineHeight: "1.125rem"
  }}>
      <div style={{
    fontWeight: 600,
    opacity: 0.72
  }}>Type</div>
      <div style={{
    overflowWrap: "anywhere"
  }}>{type}</div>
      <div style={{
    fontWeight: 600,
    opacity: 0.72,
    marginInlineStart: "0.5rem"
  }}>Default</div>
      <div style={{
    overflowWrap: "anywhere"
  }}>{default_value}</div>
      {changeable_without_restart && <div style={{
    fontWeight: 600,
    opacity: 0.72,
    marginInlineStart: "0.5rem"
  }}>
          Changeable without restart
        </div>}
      {changeable_without_restart && <div style={{
    overflowWrap: "anywhere"
  }}>
          {changeable_without_restart}
        </div>}
    </div>;
};

These settings are autogenerated from [source](https://github.com/ClickHouse/ClickHouse/blob/master/src/Core/FormatFactorySettings.h).

<h2 id="format_display_secrets_in_show_and_select">
  format\_display\_secrets\_in\_show\_and\_select
</h2>

<SettingsInfoBlock type="Bool" default_value="0" />

Enables or disables showing secrets in `SHOW` and `SELECT` queries for tables, databases,
table functions, and dictionaries.

User wishing to see secrets must also have
[`display_secrets_in_show_and_select` server setting](/docs/reference/settings/server-settings/settings#display_secrets_in_show_and_select)
turned on and a
[`displaySecretsInShowAndSelect`](/docs/reference/statements/grant#displaysecretsinshowandselect) privilege.

Possible values:

* 0 — Disabled.
* 1 — Enabled.

<h2 id="format_geojson_validate_geometry">
  format\_geojson\_validate\_geometry
</h2>

<SettingsInfoBlock type="Bool" default_value="1" />

<VersionHistory rows={[{"id": "row-1","items": [{"label": "26.7"},{"label": "1"},{"label": "New setting that controls whether the GeoJSON format enforces RFC 7946 geometry validity (minimum points per line and ring, ring closure, non-empty multi-geometries) when reading and writing"}]}]} />

Controls whether the `GeoJSON` format enforces RFC 7946 geometry validity, in both directions.

When enabled (default), a geometry that violates the GeoJSON shape rules is rejected: a `LineString` (or a line of a `MultiLineString`) with fewer than two points; a `Polygon` or `MultiPolygon` ring with fewer than four points or whose first and last points differ (an unclosed ring); or an empty `MultiLineString`, `Polygon`, or `MultiPolygon`. This applies both when reading (such a document is rejected) and when writing (such a ClickHouse value is rejected instead of producing a document the input format would reject).

When disabled, these shape rules are not enforced: such geometries are read as-is and written as-is, so degenerate geometries round-trip, but a written document may not be valid GeoJSON.

The validation is structural only: it checks point counts and ring closure. It does not inspect the geometric correctness of a shape — ring orientation (the right-hand rule / winding order) is not enforced, and structurally valid but geometrically degenerate geometries are accepted, such as a zero-area polygon, a self-intersecting ring, or a polygon whose holes lie outside its outer ring. Non-finite coordinates (`NaN`, `Inf`) are always rejected regardless of this setting, because they cannot be represented as JSON numbers.

<h2 id="format_json_object_each_row_column_for_object_name">
  format\_json\_object\_each\_row\_column\_for\_object\_name
</h2>

The name of column that will be used for storing/writing object names in [JSONObjectEachRow](/docs/reference/formats/JSON/JSONObjectEachRow) format.
Column type should be String. If value is empty, default names `row_{i}`will be used for object names.

<h2 id="format_protobuf_use_autogenerated_schema">
  format\_protobuf\_use\_autogenerated\_schema
</h2>

<SettingsInfoBlock type="Bool" default_value="1" />

Use autogenerated Protobuf when format\_schema is not set

<h2 id="format_tsv_null_representation">
  format\_tsv\_null\_representation
</h2>

<SettingsInfoBlock type="String" default_value="\N" />

Custom NULL representation in TSV format