Implied in this is that we are putting features into a dot release. I would
argue that since storage-api 2.6.0 was just released last week and has only
been adopted by ORC, we can go ahead and sneak features into the bug fix
release. Does anyone have concerns with that plan?
.. Owen
On Mon, May 7
Hi Owen,
Thanks for the help. I will work on this.
Regards,
Deepak
On 5/7/18, 4:49 PM, "Owen O'Malley" wrote:
Thanks, Deepak.
The storage-api releases are global, not specific to a single branch.
Please delete the storage-branch-2.6.1 branch, the changes that you need
sho
Thanks, Deepak.
The storage-api releases are global, not specific to a single branch.
Please delete the storage-branch-2.6.1 branch, the changes that you need
should go on the storage-branch-2.6.
Please don't copy all of the patches from branch-3 into storage-branch-2.6.
Just cherry-pick the ones
All,
Branch 3 contains changes to migrate from JAVA hash to Murmur hash (HIVE-18910)
which required addition of couple of APIs keeping the backward compatibility.
Since 2.6.0 is already released, I propose a new branch-3 only release of
storage-api.
Please let me know your thoughts on this. I a
