Hi Jim, I'm really sorry for the delay in starting the new thread for Impala branching.
Actually this time, before we port the current code of Impala, we have also thought of porting Impala's native toolchain as we'd really difficult time building it manually in past. We could build most of the tools from it. But porting "kudu" has become our major hurdle as it is equally big and challenging as that of Impala. Though we've been able to fix most of the stuff with our prior Impala experience, but everyday we see a new set of problems with kudu as we are progressing. I think once we reach near completion of porting Impala's toolchain, I will start the new thread for Impala branching as it is evolving every day. I hope we get to that state sooner. Even on contributions legal approval front, we've got the required information and we are also in the process of signing ICLA. Our filled forms have reached to IBM legal team. Hope to hear back from them soon. I thank you for your concern and once again apologize for making you follow up on this. I will definitely get back to you soon. Thanks & Regards, Nishidha From: Jim Apple <[email protected]> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS Cc: "dev@impala" <[email protected]>, Manish Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <[email protected]>, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, Valencia Serrao/Austin/Contr/IBM@IBMUS Date: 10/26/2016 01:19 AM Subject: Re: Contributions to Cloudera Impala Nishidha, I still haven't heard about the branching. Is there anything in your way I can help move aside? On Mon, Oct 3, 2016 at 8:26 AM, Jim Apple <[email protected]> wrote: >> Yes, I'll start a new discussion about branching. Could you please share the >> complete address of dev@? Is it different than >> "[email protected]"? > > That is the address.
