[
https://issues.apache.org/jira/browse/FLINK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159542#comment-14159542
]
ASF GitHub Bot commented on FLINK-1032:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/incubator-flink/pull/141#discussion_r18435533
--- Diff:
flink-compiler/src/test/java/org/apache/flink/compiler/WorksetIterationsJavaApiCompilerTest.java
---
@@ -78,7 +78,7 @@ public void
testJavaApiWithDeferredSoltionSetUpdateWithMapper() {
// verify joinWithSolutionSet
assertEquals(ShipStrategyType.PARTITION_HASH,
joinWithSolutionSetNode.getInput1().getShipStrategy());
assertEquals(ShipStrategyType.FORWARD,
joinWithSolutionSetNode.getInput2().getShipStrategy());
- assertEquals(new FieldList(0, 1),
joinWithSolutionSetNode.getKeysForInput1());
--- End diff --
Does this indicate that you found and fixed another bug on the way
(screwing up fields orders through the sorting?)
> 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: Sub-task
> Components: Java API
> Reporter: Aljoscha Krettek
> Assignee: Robert Metzger
>
> 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.3.4#6332)
