+1. Since nearly all additions to the API are likely to be extensions to the existing shuffle handler, I would like to see as much of the new stuff merged in one of two directions.
Ideally, I would like to drop the LLAP shuffle impls entirely as part of this process & streamline that into a good NM service. Cheers, Gopal On 7/19/16, 8:04 AM, "Hitesh Shah" <[email protected]> wrote: >+1 for the branch. > >Although having more contributors at times can slow things down, it might >be good to drop a note to folks on the mapreduce dev list to see if >anyone is interested in helping to contribute towards these enhancements. >This could be done potentially after the POC once we have a more clear >idea of the path being taken and a more defined list of potential >enhancements. > >thanks > Hitesh > >> On Jul 19, 2016, at 1:10 AM, Siddharth Seth <[email protected]> wrote: >> >> Sounds good. +1. >> >> On Mon, Jul 18, 2016 at 1:31 PM, Jonathan Eagles <[email protected]> >>wrote: >> >>> REQUEST TEZ-3334 feature branch creation >>> In order to prevent destabilization of master branch, I propose to >>>create a >>> feature branch TEZ-3334 that can be used to create a Custom Shuffle >>>Handler >>> for this project. Please let me know if there is any objection. >>> >>> FYI >>> After an initial POC, the project will be in a good state to quickly >>>add >>> capabilities to this feature. And sub-tasks in the JIRA will be used to >>> document current and future development. Once a proven minimal set of >>> capabilities is present, a merge request vote will be taken according >>>to >>> project by-laws. >>> >>> Regards, >>> jeagles >>> > >
