Hi Peter, - Are these patches you mention below bugfixes, or new features on Hive > 3.1.3? (This might be a typo as I think the last Hive release is 3.1.2) >
They are a collection of bug-fixes and improvements picked up from master/branch-3 branches. The list is mostly based on the additional commits found in HDP 3.1.5 and Qubole Hive 3 relative to Hive 3.1.2. I mistakenly mentioned Hive 3.1.3 because it applies up to the last few commits in branch-3.1 which set Hive version to 3.1.3 in pom.xml. We could think of the list as about 210 commits applied to Hive 3.1.2. > - Could you backport these patches to the apache branch-3, and branch-3.1? > - Is there any reason not to? > I could backport these patches to branch-3.1, but I can think of two potential problems. For branch-3, we need a separate list of commits. 1) Stability of the branch after applying these patches. As ordinary users of Hive, we cannot convince ourselves that the patches can be applied safely because we don't have definitive criteria like "everything is okay if the code passes these tests". So I think either we should be given such criteria or someone else (Hive committers) should manually inspect individual patches and test results again. 2) As our repo is essentially a fork from Hive 3.1.2, we cannot apply these patches to branch-3.1 in their current form. > I am asking this because I think the best way to move forward is to > consolidate these backports to a single repo, preferably to the apache one, > so everyone can benefit from it. > Indeed. I hope we will figure out how to make progress for this problem. Thanks, --- Sungwoo
