[
https://issues.apache.org/jira/browse/FLINK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075420#comment-14075420
]
ASF GitHub Bot commented on FLINK-1032:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/incubator-flink/pull/79#discussion_r15434384
--- Diff:
flink-core/src/main/java/org/apache/flink/types/TypeInformation.java ---
@@ -21,6 +21,10 @@
import org.apache.flink.api.common.typeutils.TypeSerializer;
public abstract class TypeInformation<T> {
+ protected final String NO_POJO_WARNING = "Field expressions can only be
used on POJOs." + " " +
+ "A POCO must have a default constructor without
arguments and not have readObject" +
--- End diff --
I think POCO is a typo.
> Extend POJO Field Selectors to Support Accessing Nested Objects
> ---------------------------------------------------------------
>
> Key: FLINK-1032
> URL: https://issues.apache.org/jira/browse/FLINK-1032
> Project: Flink
> Issue Type: Improvement
> Components: Java API
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Minor
>
> Right now you can only use fields of the top-level object as key fields in
> groupings, joins, and co-group. This should be extended to allow using nested
> fields. We have to be careful with null fields, though.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
