Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

[Aman Raj]

Hi team,

We have started working on the hive-3.2.0 release. The plan is to cut 
branch-3.2 from the base branch-3. While we were working on the 3.2.0 release, 
we found that there are some commits (Please refer to this Parent JIRA for the 
analysis - https://issues.apache.org/jira/browse/HIVE-26752) which went to 
branch-3.1 which doesn’t exist in the branch-3, same we are planning to 
backport to branch-3. There can be two approaches



  1.  Cherry-pick missed commits and push to branch-3
  2.  Create Jira's for each commit and upload patch.

Mostly we feel the second option will be better, any other thoughts will be 
appreciated.


We also need help on creating the pre-commit pipelines for branch-3 as we don’t 
have Jenkin’s access.



Please feel free to add any Jira's which you want to have to 3.2.0. All the 
changes for the 3.2.0 can be tracked here - Apache Hive - Agile Board - ASF 
JIRA

A friendly request/reminder - After this exercise if any ongoing bug fixes on 
branch-3.x should also be cherry-picked to the base branch-3

Thanks,
Aman.

[jira] [Created] (HIVE-26800) Backport HIVE-21755 : Backport HIVE-21462 to branch-3: Upgrading SQL server backed metastore when changing

[Aman Raj (Jira)]

Aman Raj created HIVE-26800:
---

 Summary: Backport HIVE-21755 : Backport HIVE-21462 to branch-3: 
Upgrading SQL server backed metastore when changing
 Key: HIVE-26800
 URL: https://issues.apache.org/jira/browse/HIVE-26800
 Project: Hive
  Issue Type: Sub-task
Reporter: Aman Raj






--
This message was sent by Atlassian Jira
(v8.20.10#820010)