[jira] [Commented] (TEZ-1503) UnorderedKVInput.getReader() should return KeyValuesReader

2014-08-26 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111095#comment-14111095 ] Gopal V commented on TEZ-1503: -- The Unordered input will not satisfy the contract of key values

[jira] [Commented] (TEZ-1503) UnorderedKVInput.getReader() should return KeyValuesReader

2014-08-26 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111245#comment-14111245 ] Bikas Saha commented on TEZ-1503: - Right. It has only 1 value per key. So logically it

[jira] [Commented] (TEZ-1503) UnorderedKVInput.getReader() should return KeyValuesReader

2014-08-26 Thread Rajesh Balamohan (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111732#comment-14111732 ] Rajesh Balamohan commented on TEZ-1503: --- If a custom processor gets different inputs

[jira] [Commented] (TEZ-1503) UnorderedKVInput.getReader() should return KeyValuesReader

2014-08-26 Thread Siddharth Seth (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111843#comment-14111843 ] Siddharth Seth commented on TEZ-1503: - Wouldn't the user typically need to process a

[jira] [Commented] (TEZ-1503) UnorderedKVInput.getReader() should return KeyValuesReader

2014-08-26 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/TEZ-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111859#comment-14111859 ] Gopal V commented on TEZ-1503: -- Yes, I think this change would make it easier to write wrong