Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.1.0
-
None
-
None
Description
This need was discussed on the mailing list [1] and will be obviated by code generation for POJO serializers and comparators [2] (as I understand, i.e., LongValue will now simply be treated as a POJO which happens to contain a long and a specialized serializer and comparator will be generated).
In the meantime, and since ValueTypeInfo will need to be reworked to use the new generators, I think it is worthwhile to add specialized serializers and comparators for the CopyableValue types.
This will also provide another point of comparison for the performance of the generated serializers and comparators.
[1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Tuple-performance-and-the-curious-JIT-compiler-td10666.html
[2] https://issues.apache.org/jira/browse/FLINK-3599
Attachments
Issue Links
- links to