Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/525#issuecomment-85422608
I think this is good to fix this.
I was wondering now whether we can actually solve this a bit more
global/local property specific. Cancelling out the properties from the non-key
fields was originally motivated by the fact that the group operation destroys
orders/groupings, which are actually local properties.
Is there a way we can preserve the global properties still?
What would happen if we move the new code that "cleans" the semantic
properties from the API operators to the optimizer's operator descriptor. There
we can filter the local properties and global properties independently.
The main benefit is probably to preserve the global properties for
`mapPartition()`, which is desirable.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
