[jira] [Created] (HIVE-26819) Vectorization: wrong results when filter on repeating map key orc table

2022-12-07 Thread Yi Zhang (Jira)
Yi Zhang created HIVE-26819:
---

 Summary: Vectorization: wrong results when filter on repeating map 
key orc table
 Key: HIVE-26819
 URL: https://issues.apache.org/jira/browse/HIVE-26819
 Project: Hive
  Issue Type: Bug
  Components: Hive
Affects Versions: 3.1.3
Reporter: Yi Zhang


Same issue is fixed by HIVE-26447, this is to fix in 3.2.0. 



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


[jira] [Created] (HIVE-26818) Beeline module misses transitive dependencies due to shading

2022-12-07 Thread Stamatis Zampetakis (Jira)
Stamatis Zampetakis created HIVE-26818:
--

 Summary: Beeline module misses transitive dependencies due to 
shading
 Key: HIVE-26818
 URL: https://issues.apache.org/jira/browse/HIVE-26818
 Project: Hive
  Issue Type: Bug
  Components: Beeline
Reporter: Stamatis Zampetakis


Due to shading, the dependecy-reduced-pom.xml file is installed in the local 
maven repository 
(~/.m2/repository/org/apache/hive/hive-beeline/4.0.0-SNAPSHOT/) for beeline. 

The latter indicates that the module doesn't have any transitive dependencies. 
If we were publishing the shaded jar that would be true but we publish the 
regular jar.

At this point, modules which include hive-beeline as a maven dependency are 
broken and problems such as HIVE-26812 may occur.

I was under the impression that these also affects 4.0.0-alpha-2 release (since 
it includes ) HIVE-25750) but strangely the published pom has all the 
dependencies:
https://repo1.maven.org/maven2/org/apache/hive/hive-beeline/4.0.0-alpha-2/hive-beeline-4.0.0-alpha-2.pom



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


[jira] [Created] (HIVE-26817) Set column names in result schema when plan has Values root

2022-12-07 Thread Krisztian Kasa (Jira)
Krisztian Kasa created HIVE-26817:
-

 Summary: Set column names in result schema when plan has Values 
root
 Key: HIVE-26817
 URL: https://issues.apache.org/jira/browse/HIVE-26817
 Project: Hive
  Issue Type: Improvement
  Components: CBO
Reporter: Krisztian Kasa
Assignee: Krisztian Kasa


The query
{code}
select b1, count(a1) count1 from (select a1, b1 from t1) s where 1=0 group by 
b1;
{code}
should have a result with column names
{code}
b1  count1
{code}
but it is
{code}
$f0 $f1
{code}



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


Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Aman Raj
Hi Ayush,

Thanks for clarifying. Will wait for it to turn green.

Thanks,
Aman.

From: Ayush Saxena 
Sent: Wednesday, December 7, 2022 3:11 PM
To: dev@hive.apache.org 
Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hi Aman,
The build is already running for your PR:
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fci.hive.apache.org%2Fblue%2Forganizations%2Fjenkins%2Fhive-precommit%2Fdetail%2FPR-3841%2F1%2Fpipeline=05%7C01%7Crajaman%40microsoft.com%7C8236b28163ba49cb063108dad8375181%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060029397272519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=BwzD%2BVXsbyWi3J%2BQgmFm7Fds2Fjtmtk9lxQE2R9%2FFio%3D=0

The JenkinsFile is picked from the PR while running rather than the target 
branch.

-Ayush

> On 07-Dec-2022, at 3:03 PM, Aman Raj  wrote:
>
> Hi Stamatis,
>
> How can we ensure that unless the PR is merged. Please suggest.
> I was thinking of merging this and raising a sample PR on branch-3 to check 
> whether it works or not. Is there some other way?
>
> Thanks,
> Aman.
> 
> From: Stamatis Zampetakis 
> Sent: Wednesday, December 7, 2022 2:51 PM
> To: dev@hive.apache.org 
> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> Hey Aman,
>
> Before checking in the PR we should ensure that it works as expected; i.e.,
> having a green run in a reasonable time.
>
> Best,
> Stamatis
>
>> On Wed, Dec 7, 2022 at 9:29 AM Aman Raj 
>> wrote:
>>
>> Hi Stamatis,
>>
>> I have raised a Pull Request for the same -
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Fpull%2F3841=05%7C01%7Crajaman%40microsoft.com%7C8236b28163ba49cb063108dad8375181%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060029397272519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=Xclf0hnvF6qeGTEJmZBuKwYdaJvhOlrlPJ1wqH1MlmA%3D=0.
>>  Can you please check this and
>> merge it.
>>
>> Thanks,
>> Aman.
>>
>> 
>> From: Aman Raj 
>> Sent: Wednesday, December 7, 2022 1:50 PM
>> To: dev@hive.apache.org 
>> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0
>> pipeline
>>
>> Hi Stamatis,
>>
>> Sure, thanks a lot for your help. Will make that change and update this
>> mail thread.
>>
>> Thanks,
>> Aman.
>> 
>> From: Stamatis Zampetakis 
>> Sent: Wednesday, December 7, 2022 1:42 PM
>> To: dev@hive.apache.org 
>> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>>
>> Hi team,
>>
>> I don't think you need any kind of special permissions to enable pre-commit
>> tests for branch-3. I have the impression that just committing an
>> appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.
>>
>> Best,
>> Stamatis
>>
>> [1]
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7C8236b28163ba49cb063108dad8375181%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060029397272519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=0qIWg4wceT9zraHfEX3lIVHiBtDezBDwWDH90Wcmgf0%3D=0
>>
>> On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
>>  wrote:
>>
>>> Hi folks,
>>>
>>> It is a blocker for us to start the Hive 3.2 release efforts. Can someone
>>> help adding Jenkins pipeline for "branch-3" or pls add "sankarh",
>> "mahesh"
>>> as admin?
>>>
>>> Thanks,
>>> Sankar
>>>
>>> -Original Message-
>>> From: Aman Raj 
>>> Sent: Monday, December 5, 2022 12:10 PM
>>> To: dev@hive.apache.org
>>> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>>>
>>> [You don't often get email from raja...@microsoft.com.invalid. Learn why
>>> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>>>
>>> Hi team,
>>>
>>> Can someone please help me set up the Jenkins pipeline for branch-3 of
>>> Hive. I do not have access to do the same and it is essential to raise
>> PR's
>>> for the 3.2.0 release. Please refer to the email thread for more details.
>>> Let me know if you need anything else from my side.
>>>
>>> Thanks,
>>> Aman.
>>> 
>>> From: Aman Raj 
>>> Sent: Friday, December 2, 2022 9:57 AM
>>> To: dev@hive.apache.org 
>>> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>>>
>>> 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 -
>>>
>> 

Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Ayush Saxena
Hi Aman,
The build is already running for your PR:
http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-3841/1/pipeline

The JenkinsFile is picked from the PR while running rather than the target 
branch.

-Ayush

> On 07-Dec-2022, at 3:03 PM, Aman Raj  wrote:
> 
> Hi Stamatis,
> 
> How can we ensure that unless the PR is merged. Please suggest.
> I was thinking of merging this and raising a sample PR on branch-3 to check 
> whether it works or not. Is there some other way?
> 
> Thanks,
> Aman.
> 
> From: Stamatis Zampetakis 
> Sent: Wednesday, December 7, 2022 2:51 PM
> To: dev@hive.apache.org 
> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
> 
> Hey Aman,
> 
> Before checking in the PR we should ensure that it works as expected; i.e.,
> having a green run in a reasonable time.
> 
> Best,
> Stamatis
> 
>> On Wed, Dec 7, 2022 at 9:29 AM Aman Raj 
>> wrote:
>> 
>> Hi Stamatis,
>> 
>> I have raised a Pull Request for the same -
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Fpull%2F3841=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rQvXSGOw6sCkHPPPn4HtLoVA9svK07WInuy%2BX0KjRI4%3D=0.
>>  Can you please check this and
>> merge it.
>> 
>> Thanks,
>> Aman.
>> 
>> 
>> From: Aman Raj 
>> Sent: Wednesday, December 7, 2022 1:50 PM
>> To: dev@hive.apache.org 
>> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0
>> pipeline
>> 
>> Hi Stamatis,
>> 
>> Sure, thanks a lot for your help. Will make that change and update this
>> mail thread.
>> 
>> Thanks,
>> Aman.
>> 
>> From: Stamatis Zampetakis 
>> Sent: Wednesday, December 7, 2022 1:42 PM
>> To: dev@hive.apache.org 
>> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>> 
>> Hi team,
>> 
>> I don't think you need any kind of special permissions to enable pre-commit
>> tests for branch-3. I have the impression that just committing an
>> appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.
>> 
>> Best,
>> Stamatis
>> 
>> [1]
>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=VZCzrTiGN4sinPmDbwCO%2BUWaxnxSmQ4b2HMLxGkxouc%3D=0
>> 
>> On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
>>  wrote:
>> 
>>> Hi folks,
>>> 
>>> It is a blocker for us to start the Hive 3.2 release efforts. Can someone
>>> help adding Jenkins pipeline for "branch-3" or pls add "sankarh",
>> "mahesh"
>>> as admin?
>>> 
>>> Thanks,
>>> Sankar
>>> 
>>> -Original Message-
>>> From: Aman Raj 
>>> Sent: Monday, December 5, 2022 12:10 PM
>>> To: dev@hive.apache.org
>>> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>>> 
>>> [You don't often get email from raja...@microsoft.com.invalid. Learn why
>>> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>>> 
>>> Hi team,
>>> 
>>> Can someone please help me set up the Jenkins pipeline for branch-3 of
>>> Hive. I do not have access to do the same and it is essential to raise
>> PR's
>>> for the 3.2.0 release. Please refer to the email thread for more details.
>>> Let me know if you need anything else from my side.
>>> 
>>> Thanks,
>>> Aman.
>>> 
>>> From: Aman Raj 
>>> Sent: Friday, December 2, 2022 9:57 AM
>>> To: dev@hive.apache.org 
>>> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>>> 
>>> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=SOVVU7Shfb4f%2Bj85chv7C%2FbUWOD%2FYLojlo3bpDPr8og%3D=0
>> )
>>> 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 

Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Aman Raj
Hi Stamatis,

How can we ensure that unless the PR is merged. Please suggest.
I was thinking of merging this and raising a sample PR on branch-3 to check 
whether it works or not. Is there some other way?

Thanks,
Aman.

From: Stamatis Zampetakis 
Sent: Wednesday, December 7, 2022 2:51 PM
To: dev@hive.apache.org 
Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hey Aman,

Before checking in the PR we should ensure that it works as expected; i.e.,
having a green run in a reasonable time.

Best,
Stamatis

On Wed, Dec 7, 2022 at 9:29 AM Aman Raj 
wrote:

> Hi Stamatis,
>
> I have raised a Pull Request for the same -
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Fpull%2F3841=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rQvXSGOw6sCkHPPPn4HtLoVA9svK07WInuy%2BX0KjRI4%3D=0.
>  Can you please check this and
> merge it.
>
> Thanks,
> Aman.
>
> 
> From: Aman Raj 
> Sent: Wednesday, December 7, 2022 1:50 PM
> To: dev@hive.apache.org 
> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0
> pipeline
>
> Hi Stamatis,
>
> Sure, thanks a lot for your help. Will make that change and update this
> mail thread.
>
> Thanks,
> Aman.
> 
> From: Stamatis Zampetakis 
> Sent: Wednesday, December 7, 2022 1:42 PM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> Hi team,
>
> I don't think you need any kind of special permissions to enable pre-commit
> tests for branch-3. I have the impression that just committing an
> appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.
>
> Best,
> Stamatis
>
> [1]
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=VZCzrTiGN4sinPmDbwCO%2BUWaxnxSmQ4b2HMLxGkxouc%3D=0
>
> On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
>  wrote:
>
> > Hi folks,
> >
> > It is a blocker for us to start the Hive 3.2 release efforts. Can someone
> > help adding Jenkins pipeline for "branch-3" or pls add "sankarh",
> "mahesh"
> > as admin?
> >
> > Thanks,
> > Sankar
> >
> > -Original Message-
> > From: Aman Raj 
> > Sent: Monday, December 5, 2022 12:10 PM
> > To: dev@hive.apache.org
> > Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
> >
> > [You don't often get email from raja...@microsoft.com.invalid. Learn why
> > this is important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > Hi team,
> >
> > Can someone please help me set up the Jenkins pipeline for branch-3 of
> > Hive. I do not have access to do the same and it is essential to raise
> PR's
> > for the 3.2.0 release. Please refer to the email thread for more details.
> > Let me know if you need anything else from my side.
> >
> > Thanks,
> > Aman.
> > 
> > From: Aman Raj 
> > Sent: Friday, December 2, 2022 9:57 AM
> > To: dev@hive.apache.org 
> > Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
> >
> > 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7Crajaman%40microsoft.com%7Cfc50a99542a94f6872c108dad8347f75%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060017264673186%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=SOVVU7Shfb4f%2Bj85chv7C%2FbUWOD%2FYLojlo3bpDPr8og%3D=0
> )
> > 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<
> >
> 

Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Stamatis Zampetakis
Hey Aman,

Before checking in the PR we should ensure that it works as expected; i.e.,
having a green run in a reasonable time.

Best,
Stamatis

On Wed, Dec 7, 2022 at 9:29 AM Aman Raj 
wrote:

> Hi Stamatis,
>
> I have raised a Pull Request for the same -
> https://github.com/apache/hive/pull/3841. Can you please check this and
> merge it.
>
> Thanks,
> Aman.
>
> 
> From: Aman Raj 
> Sent: Wednesday, December 7, 2022 1:50 PM
> To: dev@hive.apache.org 
> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0
> pipeline
>
> Hi Stamatis,
>
> Sure, thanks a lot for your help. Will make that change and update this
> mail thread.
>
> Thanks,
> Aman.
> 
> From: Stamatis Zampetakis 
> Sent: Wednesday, December 7, 2022 1:42 PM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> Hi team,
>
> I don't think you need any kind of special permissions to enable pre-commit
> tests for branch-3. I have the impression that just committing an
> appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.
>
> Best,
> Stamatis
>
> [1]
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=ZPrs%2F3lmb0PfXSVY%2FV0Q6A0OKKkJWRDmHOMuQW%2FD7uU%3D=0
>
> On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
>  wrote:
>
> > Hi folks,
> >
> > It is a blocker for us to start the Hive 3.2 release efforts. Can someone
> > help adding Jenkins pipeline for "branch-3" or pls add "sankarh",
> "mahesh"
> > as admin?
> >
> > Thanks,
> > Sankar
> >
> > -Original Message-
> > From: Aman Raj 
> > Sent: Monday, December 5, 2022 12:10 PM
> > To: dev@hive.apache.org
> > Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
> >
> > [You don't often get email from raja...@microsoft.com.invalid. Learn why
> > this is important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > Hi team,
> >
> > Can someone please help me set up the Jenkins pipeline for branch-3 of
> > Hive. I do not have access to do the same and it is essential to raise
> PR's
> > for the 3.2.0 release. Please refer to the email thread for more details.
> > Let me know if you need anything else from my side.
> >
> > Thanks,
> > Aman.
> > 
> > From: Aman Raj 
> > Sent: Friday, December 2, 2022 9:57 AM
> > To: dev@hive.apache.org 
> > Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
> >
> > 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=mI55DvBaakdMcwj%2FCgdgf9t8TrLufokftmUUN%2FSc0VE%3D=0
> )
> > 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<
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26view%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=WZmuSpezan6vNwNksAdu8NX9lIMZA9QRju6EcnBsfk0%3D=0
> > >
> >
> > 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.
> >
> >
>


Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Aman Raj
Hi Stamatis,

I have raised a Pull Request for the same - 
https://github.com/apache/hive/pull/3841. Can you please check this and merge 
it.

Thanks,
Aman.


From: Aman Raj 
Sent: Wednesday, December 7, 2022 1:50 PM
To: dev@hive.apache.org 
Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hi Stamatis,

Sure, thanks a lot for your help. Will make that change and update this mail 
thread.

Thanks,
Aman.

From: Stamatis Zampetakis 
Sent: Wednesday, December 7, 2022 1:42 PM
To: dev@hive.apache.org 
Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hi team,

I don't think you need any kind of special permissions to enable pre-commit
tests for branch-3. I have the impression that just committing an
appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.

Best,
Stamatis

[1] 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=ZPrs%2F3lmb0PfXSVY%2FV0Q6A0OKKkJWRDmHOMuQW%2FD7uU%3D=0

On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
 wrote:

> Hi folks,
>
> It is a blocker for us to start the Hive 3.2 release efforts. Can someone
> help adding Jenkins pipeline for "branch-3" or pls add "sankarh", "mahesh"
> as admin?
>
> Thanks,
> Sankar
>
> -Original Message-
> From: Aman Raj 
> Sent: Monday, December 5, 2022 12:10 PM
> To: dev@hive.apache.org
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> [You don't often get email from raja...@microsoft.com.invalid. Learn why
> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi team,
>
> Can someone please help me set up the Jenkins pipeline for branch-3 of
> Hive. I do not have access to do the same and it is essential to raise PR's
> for the 3.2.0 release. Please refer to the email thread for more details.
> Let me know if you need anything else from my side.
>
> Thanks,
> Aman.
> 
> From: Aman Raj 
> Sent: Friday, December 2, 2022 9:57 AM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=mI55DvBaakdMcwj%2FCgdgf9t8TrLufokftmUUN%2FSc0VE%3D=0)
> 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<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26view%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586=05%7C01%7Crajaman%40microsoft.com%7C55b2f70094104475ffdf08dad82bebc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059980431898757%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=WZmuSpezan6vNwNksAdu8NX9lIMZA9QRju6EcnBsfk0%3D=0
> >
>
> 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-26816) Add Jenkins file for branch-3

2022-12-07 Thread Aman Raj (Jira)
Aman Raj created HIVE-26816:
---

 Summary: Add Jenkins file for branch-3
 Key: HIVE-26816
 URL: https://issues.apache.org/jira/browse/HIVE-26816
 Project: Hive
  Issue Type: Sub-task
Reporter: Aman Raj
Assignee: Aman Raj


We should add Jenkinsfile for branch-3 so that people can file PR against it.



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


Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Aman Raj
Hi Stamatis,

Sure, thanks a lot for your help. Will make that change and update this mail 
thread.

Thanks,
Aman.

From: Stamatis Zampetakis 
Sent: Wednesday, December 7, 2022 1:42 PM
To: dev@hive.apache.org 
Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hi team,

I don't think you need any kind of special permissions to enable pre-commit
tests for branch-3. I have the impression that just committing an
appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.

Best,
Stamatis

[1] 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7Crajaman%40microsoft.com%7C02b6e30264774220677808dad82ae83a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059976080022925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=o8AeuS5vqJx6skASeTeW1j4SqtakEWYfWg49y86w4yI%3D=0

On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
 wrote:

> Hi folks,
>
> It is a blocker for us to start the Hive 3.2 release efforts. Can someone
> help adding Jenkins pipeline for "branch-3" or pls add "sankarh", "mahesh"
> as admin?
>
> Thanks,
> Sankar
>
> -Original Message-
> From: Aman Raj 
> Sent: Monday, December 5, 2022 12:10 PM
> To: dev@hive.apache.org
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> [You don't often get email from raja...@microsoft.com.invalid. Learn why
> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi team,
>
> Can someone please help me set up the Jenkins pipeline for branch-3 of
> Hive. I do not have access to do the same and it is essential to raise PR's
> for the 3.2.0 release. Please refer to the email thread for more details.
> Let me know if you need anything else from my side.
>
> Thanks,
> Aman.
> 
> From: Aman Raj 
> Sent: Friday, December 2, 2022 9:57 AM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7Crajaman%40microsoft.com%7C02b6e30264774220677808dad82ae83a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059976080022925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=x84vDkTbIjNKNZhfcaEMyBI%2BklZzHbI%2BS1uc5uCyXpI%3D=0)
> 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<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26view%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586=05%7C01%7Crajaman%40microsoft.com%7C02b6e30264774220677808dad82ae83a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059976080179130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XgPSCHloh9rrS5Vz6P2prGld8832ohl5qlnKiq6IUkM%3D=0
> >
>
> 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.
>
>


RE: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

2022-12-07 Thread Sankar Hariappan
Awesome, thanks Stamatis! Will check it out.

Thanks,
Sankar

-Original Message-
From: Stamatis Zampetakis  
Sent: Wednesday, December 7, 2022 1:43 PM
To: dev@hive.apache.org
Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline

Hi team,

I don't think you need any kind of special permissions to enable pre-commit 
tests for branch-3. I have the impression that just committing an appropriate 
Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.

Best,
Stamatis

[1] 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-24331=05%7C01%7CSankar.Hariappan%40microsoft.com%7C3fc5d66899d34179f92208dad82aee12%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059976187649126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=7esXgz7rmFr8PcAwb2gm7ukB37TT87%2BxMzq0bs2VAqU%3D=0

On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan 
 wrote:

> Hi folks,
>
> It is a blocker for us to start the Hive 3.2 release efforts. Can 
> someone help adding Jenkins pipeline for "branch-3" or pls add "sankarh", 
> "mahesh"
> as admin?
>
> Thanks,
> Sankar
>
> -Original Message-
> From: Aman Raj 
> Sent: Monday, December 5, 2022 12:10 PM
> To: dev@hive.apache.org
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 
> pipeline
>
> [You don't often get email from raja...@microsoft.com.invalid. Learn 
> why this is important at https://aka.ms/LearnAboutSenderIdentification 
> ]
>
> Hi team,
>
> Can someone please help me set up the Jenkins pipeline for branch-3 of 
> Hive. I do not have access to do the same and it is essential to raise 
> PR's for the 3.2.0 release. Please refer to the email thread for more details.
> Let me know if you need anything else from my side.
>
> Thanks,
> Aman.
> 
> From: Aman Raj 
> Sent: Friday, December 2, 2022 9:57 AM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissu
> es.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7CSankar.Haria
> ppan%40microsoft.com%7C3fc5d66899d34179f92208dad82aee12%7C72f988bf86f1
> 41af91ab2d7cd011db47%7C1%7C0%7C638059976187649126%7CUnknown%7CTWFpbGZs
> b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C3000%7C%7C%7C=gb4UBLsITXszP2jJEKvlDM1RzrfV3KcgVUNnT6dvSpU%3D&
> reserved=0) 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<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissu
> es.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26vi
> ew%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586=05%
> 7C01%7CSankar.Hariappan%40microsoft.com%7C3fc5d66899d34179f92208dad82a
> ee12%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638059976187649126%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1
> haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=dWPrdANy5ywFU%2BYGLip1Vvy%2B
> fLJc1rFFCuQipKN8KJ4%3D=0
> >
>
> 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.
>
>


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

2022-12-07 Thread Stamatis Zampetakis
Hi team,

I don't think you need any kind of special permissions to enable pre-commit
tests for branch-3. I have the impression that just committing an
appropriate Jenkinsfile (e.g., HIVE-24331 [1]) should do the trick.

Best,
Stamatis

[1] https://issues.apache.org/jira/browse/HIVE-24331

On Wed, Dec 7, 2022 at 8:41 AM Sankar Hariappan
 wrote:

> Hi folks,
>
> It is a blocker for us to start the Hive 3.2 release efforts. Can someone
> help adding Jenkins pipeline for "branch-3" or pls add "sankarh", "mahesh"
> as admin?
>
> Thanks,
> Sankar
>
> -Original Message-
> From: Aman Raj 
> Sent: Monday, December 5, 2022 12:10 PM
> To: dev@hive.apache.org
> Subject: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> [You don't often get email from raja...@microsoft.com.invalid. Learn why
> this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Hi team,
>
> Can someone please help me set up the Jenkins pipeline for branch-3 of
> Hive. I do not have access to do the same and it is essential to raise PR's
> for the 3.2.0 release. Please refer to the email thread for more details.
> Let me know if you need anything else from my side.
>
> Thanks,
> Aman.
> 
> From: Aman Raj 
> Sent: Friday, December 2, 2022 9:57 AM
> To: dev@hive.apache.org 
> Subject: [EXTERNAL] Sync of Branch-3 & Branch-3.1 for 3.2.0 pipeline
>
> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-26752=05%7C01%7CSankar.Hariappan%40microsoft.com%7Cde476c4006cf49eb3a9608dad68ba1a0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638058192487158937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2BU28qyK%2FM%2BnDk5wVGwGEr%2F7YMkx7mNw3h7iF0bdSRiU%3D=0)
> 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<
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D564%26view%3Ddetail%26selectedIssue%3DHIVE-26749%26quickFilter%3D2586=05%7C01%7CSankar.Hariappan%40microsoft.com%7Cde476c4006cf49eb3a9608dad68ba1a0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638058192487158937%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=eI19x31uSxYUbR6uXezz%2BJzg0G70hG%2BJBIbF4Qn6%2BgE%3D=0
> >
>
> 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-26815) Backport HIVE-26758 (Allow use scratchdir for staging final job) to 3.2.0

2022-12-07 Thread Yi Zhang (Jira)
Yi Zhang created HIVE-26815:
---

 Summary: Backport HIVE-26758 (Allow use scratchdir for staging 
final job) to 3.2.0
 Key: HIVE-26815
 URL: https://issues.apache.org/jira/browse/HIVE-26815
 Project: Hive
  Issue Type: Improvement
  Components: Hive
Affects Versions: 3.2.0
Reporter: Yi Zhang


HIVE-26758 add an option to allow choose set final job staging with 
hive.exec.scratchdir. This is to backport this into 3.2.0



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