Workflow [PR], commit [40643ae]

Summary: ❌

@ClickHouse/integrations-ecosystem please, take a look

@ClickHouse/integrations team, please, take a look

@Blargian Docs check fails because we have references to the deprecated Object type. I didn't find those references in the ClickHouse repository, I suspect they are in the clickhouse-docs repository. Can you please take a look and delete those references?

Good day, @Avogar !

Object type seems used in AggregateFunction when Dynamically encoded and has tag 0x14 ( https://clickhouse.com/docs/sql-reference/data-types/data-types-binary-encoding#aggregate-function-parameter-binary-encoding).

Is tag 0x14 going to be reserved and not just removed so enumeration stays unchanged?
Do Object has a dynamic type tag (I've not found in the doc)? If so - tags enumeration will not shift, too?

Thanks!

Hi @chernser!

Object type seems used in AggregateFunction when Dynamically encoded and has tag 0x14 ( https://clickhouse.com/docs/sql-reference/data-types/data-types-binary-encoding#aggregate-function-parameter-binary-encoding).
Is tag 0x14 going to be reserved and not just removed so enumeration stays unchanged?

The Object you are referring to is not a deprecated Object ClickHouse data type, it's a simple field type in the code that can store map String -> Value:

It won't be removed.

Do Object has a dynamic type tag (I've not found in the doc)? If so - tags enumeration will not shift, too?

It doesn't have it, deprecated Object type was not supported in binary types serialization because it was supposed to be removed:

Waiting for sync to finish