You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2014/01/14 06:21:51 UTC
[jira] [Commented] (TEZ-624) Fix MROutput and MROutputCommitter to
support multiple outputs
[ https://issues.apache.org/jira/browse/TEZ-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870401#comment-13870401 ]
Siddharth Seth commented on TEZ-624:
------------------------------------
I'm not sure this will actually work. The OuputCommitter, afaik, also has a role to play in determining the path. If that ends up deciding on a common work directory (based on dag_id, type-map/reduce) - a commit on another vertex also using FileOuputCommitter would be a problem.
Using vertexName - at least in it's current state - is not safe either. The unique identifier did contain the vertex name earlier, but it was removed due to the possibility of special characters etc in the vertex name. The generateId() method should give each edge a unique name - within a vertex anyway. A hash of the vertex name would likely be better if that needs to be used.
> Fix MROutput and MROutputCommitter to support multiple outputs
> --------------------------------------------------------------
>
> 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
>
>
> For users using multiple MROutput instances on a single vertex
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)