I'm not all that familiar with Clickhouse, but from the docs it looks like Tuples are basically some sort of anonymous structure so I'm guessing you'll want to encode it as a Row itself... that's a lossy conversion though so probably some sort of Logical Type that wraps the Row object is the "right answer." I'm looking at something similar right now for adding Iceberg support, though I may cheap out and just use field options to capture the original iceberg type.
On Mon, Dec 4, 2023 at 3:03 AM Mark Zitnik <m...@clickhouse.com> wrote: > Yes I know it is done in org.apache.beam.sdk.io.clickhouse.TableSchema > (Did it for several other types), but since Tuple is a nested type that can > hold any number of other ClickHouse types I was wondering what is the best > type from the Apache Beam side in order to implement it. > > Mark > > On Mon, Dec 4, 2023 at 12:24 PM Alexey Romanenko <aromanenko....@gmail.com> > wrote: > >> Hi Mark, >> >> What do you mean by “support” in this case? To map this ClickHouse data >> type to a Beam Schema data type as it’s done in >> org.apache.beam.sdk.io.clickhouse.TableSchema for other types or >> something else? >> >> — >> Alexey >> >> On 3 Dec 2023, at 10:35, Mark Zitnik <m...@clickhouse.com> wrote: >> >> Hi Team, >> >> I am one of the committers of the ClickHouse integration team. >> I need to add support for Tuple in the ClickHouse connector for >> Apache Beam. What is the best approval for implementing that? Tuple( >> https://clickhouse.com/docs/en/sql-reference/data-types/tuple) in a >> nested data type( >> https://clickhouse.com/docs/en/sql-reference/data-types#data_types). >> If you can point me to a reference on other connectors >> >> Thanks >> -MZ >> >> >> >> >>
