[
https://issues.apache.org/jira/browse/TEZ-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977129#comment-13977129
]
Bikas Saha commented on TEZ-698:
--------------------------------
I think this patch can go in as is. Since the MR helper method may be useful by
itself because it replaces a set of related helpers methods with 1 simpler
method. The methods have been written to reduce code verbosity for the simple
cases. They all accept a conf where special parameters may be set by the user.
Additional setters could be added in a follow up where they make sense. We
should definitely follow up with runtime library specific configs but it may
need some additional refactoring.
> Make it easy to create and configure
> MRInput/MROutput/ShuffleInput/SortedOutput
> -------------------------------------------------------------------------------
>
> Key: TEZ-698
> URL: https://issues.apache.org/jira/browse/TEZ-698
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-698.1.patch, TEZ-698.2.patch
>
>
> We have moved away from MR and its not necessary for anyone to write mappers
> and reducers or to configure them. But MR input and output and Shuffle
> related inputs/outputs. Currently we have to invoke a host of methods to
> configure them. If we can have a single API to make these configs then it
> would really help. Secondly for IO pairs like ShuffleInput/SortedOutput,
> their configs are related (KV types e.g.) So it maybe useful to have a
> combined API that generates configs for both in a single API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)