Github user stefanobortoli commented on the issue:
https://github.com/apache/flink/pull/3732
@fhueske, I agree with you about the risk of temporary DIST() ingestion.
Perhaps we could meanwhile just work on the "ProcessFunction + Code
generation" keeping the DIST function for test purposes tests. My concern is
that the code my change again and all the work would just be wasted. To be
honest, the code generation is quite new to me, and I will have to learn to
work on that. Meanwhile, I have almost completed a version that relies on
current code generation, nesting the distinct logic. As it is almost done, I
will share this one as well and then if necessary move to the code generation.
what do you think?
---
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.
---
