Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1483#issuecomment-171785899
Right, you cannot secure users from writing bad code, of course.
But a good way to guide then to writing good code is to expose only
information they can actually use in the abstractions provided to them.
Exposing certain information and declaring it as "don't use" is a bit like
setting them up to make mistakes, and feels like such a strong sight that the
abstractions are not picked correctly.
If this information is needed, I would really take the custom operator
variant. We could also think if there is a good way of circumventing to depend
on that channel index information in the first place.
---
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.
---
