GitHub user twalthr opened a pull request: https://github.com/apache/flink/pull/2337
[FLINK-3042] [FLINK-3060] [types] Define a way to let types create their own TypeInformation Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration. If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the [How To Contribute guide](http://flink.apache.org/how-to-contribute.html). In addition to going through the list, please provide a meaningful description of your changes. - [x] General - The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text") - The pull request addresses only one issue - Each commit in the PR has a meaningful commit message (including the JIRA id) - [ ] Documentation - Documentation has been added for new functionality - Old documentation affected by the pull request has been updated - JavaDoc for public methods has been added - [x] Tests & Build - Functionality added by the pull request is covered by tests - `mvn clean verify` has been executed successfully locally or a Travis build has passed This PR introduces so-called `TypeInfoFactory`s. A type information factory allows for plugging-in user-defined TypeInformation into the Flink type system. The factory is called during the type extraction phase if the corresponding type has been annotated with `TypeInfo` or registered globally using `TypeExtractor.registerFactory(Type, Class)`. In a hierarchy of types the closest factory will be chosen while traversing upwards, however, a globally registered factory has highest precedence. Although this PR further increases the complexity of the `TypeExtractor`. `TypeInfoFactory`s could simplify the code in future. We could implement factories for all Flink built-in types and thus split up the extraction code into type specific factories. I haven't updated the doc yet. I will add documentation after I got feedback. You can merge this pull request into a Git repository by running: $ git pull https://github.com/twalthr/flink FLINK-3042 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/2337.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2337 ---- commit 3481cf4da45292fcbf541e0ecd885a663373837b Author: twalthr <twal...@apache.org> Date: 2016-08-04T15:01:08Z [FLINK-3042] [FLINK-3060] [types] Define a way to let types create their own TypeInformation ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---