Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/867#issuecomment-115227753
We actually had a discussion about this quite a few times. I also raised my
concerns in the discussion of the issue, to which no one reacted.
The serialization subsystem (and tuples) are of the most critical nature in
Flink. There are so many side effects and considerations. Comparators that
interact with serializers, normalized keys, subclasses and tagging, object
creation (GC impact). None of that is taken into account here.
For something as crucial as this, we cannot make changes without being
discussed thoroughly before, and at best, also documented. It makes sense to do
this before the code writing.
Sorry if I appear like the bad guy here. But we are at the verge of getting
into spaghetti code and inconsistencies in one of the most crucial parts, and
we cannot do that.
---
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.
---
