Hi Hitesh, Given this change is huge and it’s easy to make mistake by missing some corner piece, I will try to get a complete list of things we need to modify before doing actual change. I’m still doing prototyping for this goal, and I’ll come back with design doc and task breakdown after finishing prototype.
Thanks! Zhiyuan > On Oct 21, 2016, at 3:22 PM, Hitesh Shah <[email protected]> wrote: > > Hello Zhiyuan, > > Thanks for volunteering to take up TEZ-1190. > > Support for multiple edges between a single pair of vertices will require > quite a few changes in the framework and therefore it does make sense to do > this in a branch. > > It would be good if you could shed some more light on how you plan to go > about this. If you have any design document ( proposals on API changes, how > to retain backward compat for existing users, etc), it would be great if you > can attach it to the jira. Once there is general agreement on the approach, > it would be great to try and break things down into separate tasks so that > other folks in the community can help out as needed. > > thanks > — Hitesh > >> On Oct 20, 2016, at 4:04 PM, zhiyuan yang <[email protected]> wrote: >> >> Hi guys, >> >> I’m going to work on TEZ-1190 which is about multiple edges between two >> vertices. What I’m gonna do is to allow user to name edge explicitly while >> keep compatibility for existing single edge cases. This requires fundamental >> changes almost everywhere, from client to AM, from AM to task. This cannot >> be achieved by one single patch of reasonable size, and it’s likely to break >> lots of other things during my work. With this in mind, I want an additional >> branch for this feature so that others won’t be mad at me :-) >> >> Thanks! >> Zhiyuan >
