Skip to content

Docs: remove references to deprecated object type #4396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 8, 2025
Merged

Docs: remove references to deprecated object type #4396

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ard/02_migrate/01_migration_guides/04_snowflake/03_sql_translation_reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Snowflake supports the `VARIANT`, `OBJECT` and `ARRAY` types for semi-structured
data.

ClickHouse offers the equivalent [`Variant`](/sql-reference/data-types/variant),
[`Object`](/sql-reference/data-types/object-data-type) (deprecated) and [`Array`](/sql-reference/data-types/array)
`Object` (now deprecated in favor of the native `JSON` type) and [`Array`](/sql-reference/data-types/array)
types. Additionally, ClickHouse has the [`JSON`](/sql-reference/data-types/newjson)
type which replaces the now deprecated `Object('json')` type and is particularly
performant and storage efficient in [comparison to other native JSON types](https://jsonbench.com/).
Expand Down
2 changes: 1 addition & 1 deletion docs/integrations/data-ingestion/data-formats/json/formats.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -348,7 +348,7 @@ Note that `JSONAsString` works perfectly fine in cases we have JSON object-per-l

## Schema for nested objects {#schema-for-nested-objects}

In cases when we're dealing with [nested JSON objects](../assets/list-nested.json), we can additionally define an explicit schema and use complex types ([`Array`](/sql-reference/data-types/array.md), [`Object Data Type`](/sql-reference/data-types/object-data-type) or [`Tuple`](/sql-reference/data-types/tuple.md)) to load data:
In cases when we're dealing with [nested JSON objects](../assets/list-nested.json), we can additionally define an explicit schema and use complex types ([`Array`](/sql-reference/data-types/array.md), [`JSON`](/integrations/data-formats/json/overview) or [`Tuple`](/sql-reference/data-types/tuple.md)) to load data:

```sql
SELECT *
Expand Down