Au-Miner opened a new pull request, #28144:
URL: https://github.com/apache/flink/pull/28144

   ## What is the purpose of the change
   
   Fix `TableEnvironment.toDataStream(..., clazz)` for POJOs that contain enum 
fields. The change makes enum fields extractable and convertible when the table 
side represents them as string values.
   
   ## Brief change log
   
   - Update `DataTypeExtractor#extractDataTypeOrError` to recognize enum 
classes via `extractEnumType`, and extend `CharType`/`VarCharType` conversion 
checks so enum classes can be bridged to string logical types.
   - Extend `DataStructureConverters#getConverterInternal` with enum handling 
for `CHAR`/`VARCHAR` and add `StringEnumConverter` to convert between 
`StringData` and enum values via `Enum.name()` / `Enum.valueOf()`.
   
   ## Verifying this change
   
   Updated `DataTypeExtractorTest` to cover plain enums, enums with additional 
fields, and POJOs containing enum fields, asserting that they are extracted as 
`STRING` bridged to the enum class. Updated `DataStructureConvertersTest` to 
verify round-trip conversion between `StringData` and enum values for string 
logical types.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to