Very good Rohini.+1 from me as well.
On Friday, September 30, 2016 1:11 PM, Rohini Palaniswamy
wrote:
Abhishek, I did rename the 4.4.0 version to 5.0.0 now. Work on a feature
branch will still be marked with the "oya" version. When it is merged, then the
Abhishek,
I did rename the 4.4.0 version to 5.0.0 now. Work on a feature branch
will still be marked with the "oya" version. When it is merged, then the
5.0.0 version can be added in addition to the "oya" version. This is
usually what is done for work in feature branches.
Peter,
It will have
+1. Pig 0.16 was the last release to support Hadoop 1.x. The next release
will not support it. Hive has already dropped it from the Hive 2.x releases.
On Fri, Sep 30, 2016 at 11:43 AM, Mohammad Islam wrote:
> Robert,Very good plan!
> How other products (pig/hive
Hi Robert,
Can you please create a fix version 5.0.0, so that OYA related stuff can be
tagged correctly.
Thanks,
Abhishek
> On Oct 1, 2016, at 12:13 AM, Mohammad Islam
> wrote:
>
> Robert,Very good plan!
> How other products (pig/hive etc) are handling the Hadoop
Robert,Very good plan!
How other products (pig/hive etc) are handling the Hadoop 1 issue?If they are
planning in the same way, this will be easy for us.
Regards,Mohammad
On Thursday, September 29, 2016 5:56 PM, Robert Kanter
wrote:
Hi,
Now that Oozie 4.3 is
Hi,
one question from me: how shall we integrate our OYA changes to master?
I can think of four options:
1. Simply git merge our commits from the oya branch. This will mean at
least 20-30 commits.
2. We squash our commits to have fewer and then merge the oya branch (right
now I can't say in
Hi,
Now that Oozie 4.3 is branched and will be happening soon, I imagine the
next release we do with be Oozie 5 with Oozie On Yarn. We can continue to
keep OYA in a feature branch until later when it's more stable so we don't
disrupt the master branch in the meantime. We've already removed 0.23