You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched in the issues and found nothing similar.
Motivation
Hello team,
I would like to request support for the ENUM type in the Debezium format, which is currently supported in Avro. Reference for the Avro Enum type implementation: Schema.java.
Solution
Currently, Flink treats enums as STRING by default. More specifically, "Avro enums have limited support. Flink supports reading and writing enums but treats them as a STRING type. From Flink's perspective, enums are not distinguishable from the STRING type. You can't create an Avro schema from Flink that has an enum field." Source: Flink Serialization Docs.
To provide similar support in Paimon, I believe that modifying the code to handle enums just as STRING types could work. For example, adding the following case in the Debezium schema utils:
case ENUM:
case STRING:
return DataTypes.STRING();
Search before asking
Motivation
Hello team,
I would like to request support for the ENUM type in the Debezium format, which is currently supported in Avro. Reference for the Avro Enum type implementation: Schema.java.
Solution
Currently, Flink treats enums as STRING by default. More specifically, "Avro enums have limited support. Flink supports reading and writing enums but treats them as a STRING type. From Flink's perspective, enums are not distinguishable from the STRING type. You can't create an Avro schema from Flink that has an enum field." Source: Flink Serialization Docs.
To provide similar support in Paimon, I believe that modifying the code to handle enums just as STRING types could work. For example, adding the following case in the Debezium schema utils:
This change can be made in DebeziumSchemaUtils.java.
Thanks let me know if something is unclear in this request.
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: