Hi Alexander,
I guess that Timo will be able to give a more detailed answer, but I agree
with your assessment. The TypeInfo annotation does not solve all the
problems as you've stated. Thus, making the TypeExtractor.registerFactory
method public would solve the problem. I'm just wondering whether
To follow up on my on post,
I think a straight-forward approach would be to make the
`TypeExtractor.registerFactory` method public [1].
BTW, both the TypeInfo annotation [2] and TypeInfoFactory [3] itself refer
to this method in the JavaDoc. However, besides these mentions I was not
able to find
I wanted to open this directly as a JIRA to follow-up on FLINK-3042,
however my account (aalexandrov) does not seem to have the necessary
privileges, so I will post this to the dev list instead.
The current approach for registration of custom `TypeInformation`
implementations which relies exclusiv
