[
https://issues.apache.org/jira/browse/FLINK-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248874#comment-16248874
]
Gabor Gevay commented on FLINK-4575:
------------------------------------
[~vcycyv], I'm not sure how would {{getFlatFields}} help here. (How would you
convert back to POJO at the end?)
But if you would like to work on this jira, then the approach outlined in the
jira description should work. I think this is the cleanest solution, since
{{FieldAccessor}} is exactly for situations like we have here, where we have to
get and set a field, based on a field expression. However, you would have to
resolve https://issues.apache.org/jira/browse/FLINK-4578 first. I think that
could be resolved by the solution that I wrote in a comment there.
> DataSet aggregate methods should support POJOs
> ----------------------------------------------
>
> Key: FLINK-4575
> URL: https://issues.apache.org/jira/browse/FLINK-4575
> Project: Flink
> Issue Type: Improvement
> Components: DataSet API
> Reporter: Gabor Gevay
> Priority: Minor
> Labels: starter
>
> The aggregate methods of DataSets (aggregate, sum, min, max) currently only
> support Tuples, with the fields specified by indices. With
> https://issues.apache.org/jira/browse/FLINK-3702 resolved, adding support for
> POJOs and field expressions would be easy: {{AggregateOperator}} would create
> {{FieldAccessors}} instead of just storing field positions, and
> {{AggregateOperator.AggregatingUdf}} would use these {{FieldAccessors}}
> instead of the Tuple field access methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
