S3 Sink Connector header schema


Im running an S3 Sink Connector and have a custom Partitioner, that maps records based on some kafka message header values. The headers are parsed into different datatypes and in my specific case, a string is misinterpreted as an integer and that results in the removal of leading zeros. Is there a way to enforce the header schemas to always be String or byte arrays?

Thanks a lot