You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gabor Gevay (JIRA)" <ji...@apache.org> on 2016/09/04 19:11:20 UTC

[jira] [Commented] (FLINK-4575) DataSet aggregate methods should support POJOs

    [ https://issues.apache.org/jira/browse/FLINK-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463360#comment-15463360 ] 

Gabor Gevay commented on FLINK-4575:
------------------------------------

This is a bit harder than I thought, because of adding the ForwardedFields property in case of the aggregation field not being the same as the key field. Note, that the old logic of determining this has a bug: https://issues.apache.org/jira/browse/FLINK-4578

> 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.3.4#6332)