Skip to content
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.

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

Allow configuration of NULL value replacement during Avro file creation #381

Open
ebrard opened this issue Aug 29, 2024 · 0 comments
Open

Comments

@ebrard
Copy link

ebrard commented Aug 29, 2024

As of now, when the format class is set to format.class=io.confluent.connect.s3.format.avro.AvroFormat, the configuration value used for ignore.default.for.nullables is the default false. There seems to be no way to turn it to true since this configuration parameter is not referenced in the sink task configuration (as opposed to enhanced.avro.schema.support which can be turned ON or OFF).

This means that a null-value which has a default will have it set to the default in the Avro file dumped in S3 for example whereas the same record in Kafka will be properly set to NULL.

Could the sink task configuration be extended to support passing the ignore.default.for.nullables parameter down to the AvroFormat class (through AvroDataConfig apparently)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant