[
https://issues.apache.org/jira/browse/TEZ-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876799#comment-13876799
]
Bikas Saha commented on TEZ-624:
--------------------------------
bq. Should getTaskIndex / getOutputIndex be setup as explicit APIs. If these
are exposed, we should likely get rid of getUniqueIdentifier, and let users
construct that on their own (and expose InputIndex as well for consistency).
Alternately, uniqueIdentifier could just be changed to be
vertexId_IOIndex_taskIndex.
getTaskIndex() is already exposed. We could get rid of uniqueIdentifier or
change it. Separate patch IMO.
Modified the javadoc a bit. Made number format object member. So its one per
output object. Used different number format for vertices and outputs with 3.
> Fix MROutput to support multiple outputs to the same output location
> --------------------------------------------------------------------
>
> Key: TEZ-624
> URL: https://issues.apache.org/jira/browse/TEZ-624
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Bikas Saha
> Attachments: TEZ-624.1.patch, TEZ-624.2.patch, TEZ-624.3.patch
>
>
> For users using multiple MROutput instances on a single vertex
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
