Github user ggevay commented on the issue:
https://github.com/apache/flink/pull/2094
> I am a bit out of the loop here. Why do we need a field accessor in the
TypeInformation?
We need this for situations when the user specifies a nested field
expression, which goes through different types. (E.g. `.sum("foo.f1.bar")` on a
POJO, where the field `foo` is a Tuple, and `f1` is a POJO again.) In this
case, getFieldAccessor can recursively call itself on the TypeInformation of
the field, which will be a virtual call that goes to the override for the
field's type.
---
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.
---
