Paultagoras

This is an interesting problem - on the one hand, we do the inserts serially for data integrity reasons. On the other, maybe there are performance gains around parallel processing...

Hmm, that's interesting - I'll have to see if we can set that, we don't control the wider Connect framework though (where those settings are resolved)

Hi @vladislav-bakanov ! So oddly enough, when I mess around with the consumer/producer configs (but leave the connector property configured) it gives me the errors I'd expect. Do you happen...

@vladislav-bakanov Unfortunately if this is related to the Kafka Connect configuration, it's out of our control - and in cloud environments (like Confluent Cloud or MSK) those environment values are...

Unfortunately this isn't something we can really log - it's part of the overall Kafka Connect framework (and whichever environment it lives in) so I'm going to close this. If...

@nicolae-gorgias I don't believe we have specific memory settings, but one thing I would suggest is updating the version - we've just released 1.0.8 and (especially compared to 0.0.14) there...

Hmm interesting - I'll have to take another look. We don't control/configure memory usage to my knowledge, that's all handled by Kafka Connect, but maybe there's some flag or something...

Hi @amit-cashify - the short answer is that we're waiting for official support of the [JSON](https://clickhouse.com/docs/en/sql-reference/data-types/json) type, as it's currently considered experimental. There are a few workarounds for this -...

> > Hi @amit-cashify - the short answer is that we're waiting for official support of the [JSON](https://clickhouse.com/docs/en/sql-reference/data-types/json) type, as it's currently considered experimental. > > I am also waiting...

According to https://clickhouse.com/docs/en/sql-reference/data-types/json this is an obsolete type and no longer meant to be used, as such closing this issue.