Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/311#issuecomment-70517390
IMO, users should only be allowed to set semantic properties though field
expression strings. There should be no need to implement an own
SemanticProperty class or manually set the forwarded fields in SemanticProperty
objects. Setting these fields is not trivial because of field indices needs to
be flattened and types of source and target fields should be checked for
compatibility. From my point of view, this is clearly a developer API. Whoever
gets in touch with it should not have problems dealing with input ids or
implementing the backwards access.
The {{hasFieldForwardInfomation()}} can be removed though. Will 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 [email protected] or file a JIRA ticket
with INFRA.
---
