Major Description
Currently, introducing new Types that should have specific TypeInformation requires
- Either integration with the TypeExtractor
- Or manually constructing the TypeInformation (potentially at every place) and using type hints everywhere.
I propose to add a way to allow classes to create their own TypeInformation (like a static method "createTypeInfo()").
To support generic nested types (like Optional / Either), the type extractor would provide a Map of what generic variables map to what types (deduced from the input). The class can use that to create the correct nested TypeInformation (possibly by calling the TypeExtractor again, passing the Map of generic bindings).
Attachments
Issue Links
- is depended upon by
-
FLINK-3695 ValueArray types
-
- Closed
-
- links to
