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, 2018 at 4:49 PM, Owen O'Malley <owen.omal...@gmail.com> 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 > 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 that touched storage-api. > > % git log --format=oneline rel/storage-release-2.6.0..apache/branch-3 > storage-api/ > > shows that we 6 potential patches: > > 54651c783bef724713739e59b0d79672a60c6a2c HIVE-18910 : Migrate to Murmur > hash for shuffle and bucketing > cdd31fab6eb51e319df03bff880274dc66dd1c39 HIVE-18988: Support bootstrap > replication of ACID tables > ea18769f026429ea6ebbbd66858920ebf869a9d6 HIVE-19124 : implement a basic > major compactor for MM tables > a39b24660127ace7459ea1598b12d8add1f7b783 HIVE-19226: Extend storage-api > to print timestamp values in UTC > bbb8e27bc8b7c7592f45c1e5ffc2ca00b6db6820 HIVE-19226: Extend storage-api > to print timestamp values in UTC > 624e464a2cc4fe4dd9395edf8b377fd7323a299e HIVE-19126: CachedStore: Use > memory estimation to limit cache size during prewarm > > so those are the ones to consider. > > .. Owen > > On Mon, May 7, 2018 at 4:19 PM, Deepak Jaiswal <djais...@hortonworks.com> > wrote: > >> 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 am working on the release >> candidate. >> >> Regards, >> Deepak >> > >