The current Confluent Cloud connector supports 4 message types: JSON, Avro, Protobuf, and Text. This feature request is for this connector to also support JSON_SR message types.
Relevant Fivetran reply from the original ticket diagnosing our Confluent connector issue:
According to our engineering team, messages encoded in JSON_SR format will have schema_id and magic byte appended to the start of the message.
We currently do no support this.
Without JSON_SR support every user currently receiving JSON_SR message types has to default to syncing their data as Text. This means creating an additional custom ETL layer which dynamically determines the schema of the message and unpacks its contents. These are exactly the kind of extra steps we expect Fivetran to be capable of handling and, so, is why we are submitting this request.