Re: [ANNOUNCE] Apache Hive 4.0.0 Released

[Battula, Brahma Reddy]

Thank you for your hard work and dedication in releasing Apache Hive version 
4.0.0.

Congratulations to the entire team on this achievement. Keep up the great work!

Does this consider as GA.?

And Looks we need to update in the following location also.?
https://hive.apache.org/general/downloads/


From: Denys Kuzmenko 
Date: Saturday, March 30, 2024 at 00:07
To: u...@hive.apache.org , dev@hive.apache.org 

Subject: [ANNOUNCE] Apache Hive 4.0.0 Released

The Apache Hive team is proud to announce the release of Apache Hive

version 4.0.0.



The Apache Hive (TM) data warehouse software facilitates querying and

managing large datasets residing in distributed storage. Built on top

of Apache Hadoop (TM), it provides, among others:



* Tools to enable easy data extract/transform/load (ETL)



* A mechanism to impose structure on a variety of data formats



* Access to files stored either directly in Apache HDFS (TM) or in other

  data storage systems such as Apache HBase (TM)



* Query execution via Apache Hadoop MapReduce, Apache Tez and Apache Spark 
frameworks. (MapReduce is deprecated, and Spark has been removed so the text 
needs to be modified depending on the release version)



For Hive release details and downloads, please visit:

https://hive.apache.org/downloads.html



Hive 4.0.0 Release Notes are available here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343343=Text=12310843



We would like to thank the many contributors who made this release

possible.



Regards,



The Apache Hive Team

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

[Battula, Brahma Reddy]

Hi Stamatis,

Any further update on the following which we missed here. thanks


Regards,
Brahma.


From: Stamatis Zampetakis 
Date: Tuesday, August 1, 2023 at 17:05
To: dev@hive.apache.org 
Subject: Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Hello,

HIVE-27504 is now merged to master. Thanks everyone for the reviews!

I am going to prepare the release candidate for 4.0.0-beta-1 sometime this week.

Best,
Stamatis

On Thu, Jul 27, 2023 at 1:54 PM Battula, Brahma Reddy
 wrote:
>
> Looks following PR is reviewed. Any chance to get it merged and give the 
> release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis"  <mailto:zabe...@gmail.com>> wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30/07. If HIVE-27504 does not land in the next day or two the beta-1
> release might get delayed unless someone else picks up the RM role and
> cuts the RC.
>
>
> Best,
> Stamatis
>
>
> On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
>  <mailto:aturo...@cloudera.com.inva>lid<mailto:aturo...@cloudera.com.inva%3elid>>
>  wrote:
> >
> > Thanks for the update! Can't wait for the beta :)
> >
> > -Attila
> >
> > On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis  > <mailto:zabe...@gmail.com>>
> > wrote:
> >
> > > Hey everyone,
> > >
> > > As you may have noticed there have been various tickets around LICENSE
> > > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > > which hopefully addresses all remaining issues that were found while I
> > > was working with the RC. After this gets resolved we should be good to
> > > go for putting up the RC for vote.
> > >
> > > The structure and content of the LICENSE and NOTICE file are very
> > > important for Apache releases so I would encourage other members of
> > > the community (especially PMC) to review the latest changes and
> > > current status and raise new JIRA tickets if they discover some
> > > problems. I would like to avoid having last minute -1 votes due to
> > > that.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] 
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D=0<https://issues.apache.org/jira/browse/HIVE-27504>
> > >  
> > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D=0<https://issues.apache.org/jira/browse/HIVE-27504>>
> > >
> > > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  > > <mailto:zabe...@gmail.com>>
> > > wrote:
> > > >
> > > > Hey team,
> > > >
> > > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > > >
> > > > Most of the release steps went out smoothly and I was able to get an
> > > > RC0 ready [1].
> > > >
> > > > However, I am afraid that our binary distribution does not comply
> > > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > > within and I am not sure if we are fully covered in terms of licenses
> > > > and notice files. Thanks Ayush for reminding me to check the
> > > > binary-package-licenses directory [5].
> > > >
> > > > I am checking various resources such as [3, 4] to see what additional
> > > > steps we can take to be on the safe side and also looking for ways to
> > > > automate this so that we don't have to manually inspect the jars on
> > > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > > am not yet completely happy with its output.
> > > >
> > > > The next few days will be a bit busy so most likely I will get back on
> > > > this during the weekend. If people have feedback or other ideas to
> > > > share please let me know.
> > > >
> >

Re: [ANNOUNCE] Apache Hive 4.0.0-beta-1 Released

[Battula, Brahma Reddy]

Nice!! Thanks to all who all make this happen..

Any draft plan GA for 4.0.0. ( If it's already discussed, please provide the 
reference.)


On 15/08/23, 12:13 PM, "Stamatis Zampetakis" mailto:zabe...@apache.org>> wrote:


The Apache Hive team is proud to announce the release of Apache Hive
version 4.0.0-beta-1.


The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage. Built on top
of Apache Hadoop (TM), it provides, among others:


* Tools to enable easy data extract/transform/load (ETL)


* A mechanism to impose structure on a variety of data formats


* Access to files stored either directly in Apache HDFS (TM) or in other
data storage systems such as Apache HBase (TM)


* Query execution via Apache Tez Frameworks.


For Hive release details and downloads, please visit:
https://hive.apache.org/downloads.html 


Hive 4.0.0-beta-1 Release Notes are available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353351=Text=12310843
 



We would like to thank the many contributors who made this release
possible.


Regards,


The Apache Hive Team

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

[Battula, Brahma Reddy]

Looks following PR is reviewed. Any chance to get it merged and give the 
release.?

On 18/07/23, 2:39 PM, "Stamatis Zampetakis" mailto:zabe...@gmail.com>> wrote:


HIVE-27504 still lacks reviews from committers.


Note that I will not be able to work on the release from 22/07 to
30/07. If HIVE-27504 does not land in the next day or two the beta-1
release might get delayed unless someone else picks up the RM role and
cuts the RC.


Best,
Stamatis


On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
mailto:aturo...@cloudera.com.inva>lid> wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis  >
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various tickets around LICENSE
> > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > which hopefully addresses all remaining issues that were found while I
> > was working with the RC. After this gets resolved we should be good to
> > go for putting up the RC for vote.
> >
> > The structure and content of the LICENSE and NOTICE file are very
> > important for Apache releases so I would encourage other members of
> > the community (especially PMC) to review the latest changes and
> > current status and raise new JIRA tickets if they discover some
> > problems. I would like to avoid having last minute -1 votes due to
> > that.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-27504 
> > 
> >
> > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  > >
> > wrote:
> > >
> > > Hey team,
> > >
> > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > >
> > > Most of the release steps went out smoothly and I was able to get an
> > > RC0 ready [1].
> > >
> > > However, I am afraid that our binary distribution does not comply
> > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > within and I am not sure if we are fully covered in terms of licenses
> > > and notice files. Thanks Ayush for reminding me to check the
> > > binary-package-licenses directory [5].
> > >
> > > I am checking various resources such as [3, 4] to see what additional
> > > steps we can take to be on the safe side and also looking for ways to
> > > automate this so that we don't have to manually inspect the jars on
> > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > am not yet completely happy with its output.
> > >
> > > The next few days will be a bit busy so most likely I will get back on
> > > this during the weekend. If people have feedback or other ideas to
> > > share please let me know.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/ 
> > > 
> > > [2]
> > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> >  
> > 
> > > [3] https://infra.apache.org/licensing-howto.html 
> > > 
> > > [4] https://www.apache.org/legal/resolved.html 
> > > 
> > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses 
> > > 
> > > [6] https://www.mojohaus.org/license-maven-plugin/ 
> > > 
> > >
> > >
> > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis  > > >
> > wrote:
> > > >
> > > > I can start preparing the RC towards the end of next week. If somebody
> > > > has more time and wants to start earlier I am fine to switch.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  > > > >
> > wrote:
> > > > >
> > > > > great, this is the current list of release managers:
> > > > >
> > > > > 4.0.0 Stamatis Zampetakis
> > > > > 4.1.0 Denys Kuzmenko
> > > > > 4.2.0 Sai Hemanth Gantasala
> > > > >
> > > > > Should we keep the same RM order and just shift the releases or find
> > a volunteer for the 4.0.0-beta release, WDYT?
> > > > >
> > > > >
> >

Re: ODBC Driver for Hive

[Battula, Brahma Reddy]

There are attempts on hive-1[1][2] and then later these are not maintained.  
Any pointers to this.?


1. https://issues.apache.org/jira/browse/HIVE-187
2. https://issues.apache.org/jira/browse/HIVE-1101


On 23/11/22, 11:03 PM, "Battula, Brahma Reddy"  
wrote:

Hi All,

Is there any opensource ODBC Drivers for hive, Any leads would be 
appreciated.



Regards,
Brahma

ODBC Driver for Hive

[Battula, Brahma Reddy]

Hi All,

Is there any opensource ODBC Drivers for hive, Any leads would be appreciated.



Regards,
Brahma

Re: TPCDS query degrade with hive-3.1.2 because of wrong estimation for reducers

[Battula, Brahma Reddy]

db1c477d76%7C0%7C0%7C638003523457672652%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=AZcLqHcduwJCNoSrPq3XULhuKyX1EueVrso7zNFFuWY%3D=0>
https://issues.apache.org/jira/browse/HIVE-23485<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-23485=05%7C01%7Cbbattula%40visa.com%7C1978a7adfb6a494768ba08daa4d3019f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638003523457672652%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=fEw7VqFhGZM52jdUN%2B4ZZf2bGdloWro2XLdPxwLr2i0%3D=0>

On Sun, Oct 2, 2022 at 1:56 PM Battula, Brahma Reddy 
mailto:bbatt...@visa.com>> wrote:
+ Attaching the hs2 logs also.

From: "Battula, Brahma Reddy" mailto:bbatt...@visa.com>>
Date: Sunday, 2 October 2022 at 2:16 AM
To: "u...@hive.apache.org<mailto:u...@hive.apache.org>" 
mailto:u...@hive.apache.org>>
Subject: TPCDS query degrade with hive-3.1.2 because of wrong estimation for 
reducers

Hi All,

We’ve ran TPCDS queries against hive-3.1.2 and trunk(little older version). 
(Attached files suffix “a” is trunk and “v” is 3.1.2)

The query execution time is higher in hive-3.1.2 as number of the reducers 
estimated is less (8) as compared to trunk version where it’s 46.

All the hive/tez/Yarn configs are same in both clusters. Even h/w resources are 
same. And query planner is also same.

The stats in reduce sink phase are not look same.

HIVE_TRUNK_CODE - 2022-09-26T05:58:23,786 INFO  
[07243354-f941-419d-8908-45009762e67d HiveServer2-Handler-Pool: Thread-168]: 
optimizer.ConvertJoinMapJoin (:()) - Join input#1; onlineDataSize:   9628; 
Statistics: Num rows:  359 Data size: 4308  Basic stats: COMPLETE Column stats: 
COMPLETE
HIVE_3.1.2_CODE - 2022-09-27T03:39:45,116 INFO  
[2fd1493c-f1a0-4874-acac-58f28e9c21ea HiveServer2-Handler-Pool: Thread-134]: 
optimizer.ConvertJoinMapJoin (:()) - Join input#1; onlineDataSize: 325856; 
Statistics: Num rows: 8116 Data size: 97392 Basic stats: COMPLETE Column stats: 
COMPLETE

Any idea how the reducers getting underestimated.?

Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x

[Battula, Brahma Reddy]

Agree to Peter and sunchao..

Even we are using the hive 3.x, we might contribute on bugfixes. 

Even I am +1 on 1.x EOL as it's hard to maintain so many releases and time to 
user's migrate to 2.x and 3.x.


On 09/05/22, 10:51 PM, "Chao Sun"  wrote:

Agree to Peter above. I know quite a few projects such as Spark,
Iceberg and Trino/Presto are depending on Hive 2.x and 3.x, and
periodically they may need new fixes in these. Upgrading them to use
4.x seems not an option for now since the core classified artifact has
been removed and the shading issue has to be solved before they can
consume the new jar.

On Mon, May 9, 2022 at 4:10 AM Peter Vary  wrote:
>
> Hi Team,
>
> My experience with the Iceberg community shows that there are some 
sizeable userbase around Hive 2.x. I have seen patches, contributions to Hive 
2.3.x branches, and the tests are in much better shape there.
>
> I would definitely vote for EOL Hive 1.x, but until we have a stable 4.x, 
I would be cautious about slashing 2.x, 3.x branches.
>
> Just my 2 cents.
>
> Peter
>
> On 2022. May 9., at 10:51, Alessandro Solimando 
 wrote:
>
> Hi Stamatis,
> thanks for bringing up this topic, I basically agree on everything you 
wrote.
>
> I just wanted to add that this kind of proposal might sound harsh, 
because in many contexts upgrading is a complex process, but it's in nobody's 
interest to keep release branches that are missing important fixes/improvements 
and that might not meet the quality standards that people expect, as mentioned.
>
> Since we don't have yet a stable 4.x release (only alpha for now) we 
might want to keep supporting the 3.x branch until the first 4.x stable release 
and EOL < 3.x branches, WDYT?
>
> Best regards,
> Alessandro
>
> On Fri, 6 May 2022 at 23:14, Stamatis Zampetakis  
wrote:
>>
>> Hi all,
>>
>> The current master has many critical bug fixes as well as important 
performance improvements that are not backported (and most likely never will) 
to the maintenance branches.
>>
>> Backporting changes from master usually requires adapting the code and 
tests in questions making it a non-trivial and time consuming task.
>>
>> The ASF bylaws require PMCs to deliver high quality software which 
satisfy certain criteria. Cutting new releases from maintenance branches with 
known critical bugs is not compliant with the ASF.
>>
>> CI is unstable in all maintenance branches making the quality of a 
release questionable and merging new PRs rather difficult. Enabling and running 
it frequently in all maintenance branches would require a big amount of 
resources on top of what we already need for master.
>>
>> History has shown that it is very difficult or impossible to properly 
maintain multiple release branches for Hive.
>>
>> I think it would be to the best interest of the project if the PMC 
decided to drop support for maintenance branches and focused on releasing 
exclusively from master.
>>
>> This mail is related to the discussion about the release cadence [1] 
since it would certainly help making Hive releases more regular. I decided to 
start a separate thread to avoid mixing multiple topics together.
>>
>> Looking forward to your thoughts.
>>
>> Best,
>> Stamatis
>>
>> [1] 
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fn245dd23kb2v3qrrfp280w3pto89khxjdata=05%7C01%7Cbbattula%40visa.com%7Ccba1383657724a00f0bb08da31e069bc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637877137169408371%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=X3BJyzgALXZVnjmd2PzbLrOi4lXMHxEQa8KwA1Pz7BQ%3Dreserved=0
>>
>

Re: [ANNOUNCE] New committer: Ayush Saxena

[Battula, Brahma Reddy]

Congratulations Ayush Saxena!! Well Deserved!.

From: László Bodor 
Date: Monday, 7 February 2022 at 9:20 PM
To: dev@hive.apache.org 
Subject: Re: [ANNOUNCE] New committer: Ayush Saxena
Welcome Ayush, well deserved!

Ashutosh Chauhan  ezt írta (időpont: 2022. febr. 7.,
H, 16:35):

> Hi all,
> Apache Hive's Project Management Committee (PMC) has invited Ayush
> to become a committer, and we are pleased to announce that he has accepted!
>
> Ayush welcome, thank you for your contributions, and we look forward to
> your
> further interactions with the community!
> Ashutosh (on behalf of Hive PMC)
>

Re: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to CVE-2021-44228

[Battula, Brahma Reddy]

Yes, Looks PR Got raised for same which I missed earlier mail. Hopefully it 
will get merge soon.

And to answer your following question.

But not sure the change on below file:
 
ql/src/java/org/apache/hadoop/hive/ql/log/SlidingFilenameRolloverStrategy.java


SlidingFilenameRolloverStrategy implements (inherit) 
DirectFileRolloverStrategy…  As part of the following fix, 
clearCurrentFileName(.) is introduced in DirectFileRolloverStrategy, which is 
merged in 2.11.2 and 3.0.0 .. And we are migration from 2.8.2 hence this method 
is added.


https://issues.apache.org/jira/browse/LOG4J2-1906

https://github.com/apache/logging-log4j2/blob/42aa6aeb54a2d179b0271c09b450ca3d18c3a7a8/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/DirectFileRolloverStrategy.java#L26


Hope this clarifies you.. And  even you can ask in the PR’s, if you’ve any 
other doubts!!..






--Brahma Reddy Battula


From: Sundaram, Ramakrishnan 
Date: Thursday, 16 December 2021 at 11:48 AM
To: dev@hive.apache.org 
Cc: secur...@hive.apache.org 
Subject: Re: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to 
CVE-2021-44228
Makes sense.
Also I see commit on branch-3: 
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Fpull%2F2869%2Ffilesdata=04%7C01%7Cbbattula%40visa.com%7C83594aaff03c46434a2908d9c05bd413%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637752322905589191%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=tspHne30%2F3CSx8J9OmgU6EAtDTwoB0cWTNP4GsxGOwo%3Dreserved=0

Details:

[hive] branch branch-3 updated: HIVE-25795: Update log4j2 version to 2.16.0 for 
branch-3 (Naveen Gangam)

ngangam pushed a commit to branch branch-3
in repository 
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Fhive.gitdata=04%7C01%7Cbbattula%40visa.com%7C83594aaff03c46434a2908d9c05bd413%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637752322905589191%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=QN%2BvgZrXE15rZ9LYcRiV7DHPRWoQPRGywtaX4KCtb4E%3Dreserved=0


The following commit(s) were added to refs/heads/branch-3 by this push:
 new 63a056a  HIVE-25795: Update log4j2 version to 2.16.0 for branch-3 
(Naveen Gangam)
63a056a is described below

commit 63a056ae87de739ba2ea66fd4001f529357a4aa1
Author: Naveen Gangam 
AuthorDate: Wed Dec 15 15:57:45 2021 -0500

HIVE-25795: Update log4j2 version to 2.16.0 for branch-3 (Naveen Gangam)
--

But not sure the change on below file:
ql/src/java/org/apache/hadoop/hive/ql/log/SlidingFilenameRolloverStrategy.java

Regards,
Ram


On 12/15/21, 8:29 PM, "Battula, Brahma Reddy"  
wrote:

it’s committed only for master where we dn’t have this.

Only for branch-2 and branch-3, we need to handle this file. Please see, 
following discussion for same..

https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhive%2Fpull%2F2863data=04%7C01%7Cbbattula%40visa.com%7C83594aaff03c46434a2908d9c05bd413%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637752322905589191%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=j0Sibu5k6V1eYUijQLpjlI83j3I9Ci07Zo9t9gn4Zxo%3Dreserved=0

If you are interested, you raise PR for branch-2 and branc-3.


From: Sundaram, Ramakrishnan 
Date: Thursday, 16 December 2021 at 3:05 AM
To: dev@hive.apache.org 
Cc: secur...@hive.apache.org 
Subject: Re: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to 
CVE-2021-44228
+ security

From: "Sundaram, Ramakrishnan" 
Date: Wednesday, December 15, 2021 at 1:32 PM
To: "dev@hive.apache.org" 
Subject: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to 
CVE-2021-44228

Hi,
I see in HIVE-25804 and HIVE-25795, testutils/ptest2/pom.xml is not 
upgraded to latest versions.
Is this a miss? Or the change is not needed?

Regards,
Ram

Re: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to CVE-2021-44228

[Battula, Brahma Reddy]

it’s committed only for master where we dn’t have this.

Only for branch-2 and branch-3, we need to handle this file. Please see, 
following discussion for same..
https://github.com/apache/hive/pull/2863

If you are interested, you raise PR for branch-2 and branc-3.


From: Sundaram, Ramakrishnan 
Date: Thursday, 16 December 2021 at 3:05 AM
To: dev@hive.apache.org 
Cc: secur...@hive.apache.org 
Subject: Re: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to 
CVE-2021-44228
+ security

From: "Sundaram, Ramakrishnan" 
Date: Wednesday, December 15, 2021 at 1:32 PM
To: "dev@hive.apache.org" 
Subject: Regarding log4j2 upgrade: HIVE-25804, HIVE-25795 related to 
CVE-2021-44228

Hi,
I see in HIVE-25804 and HIVE-25795, testutils/ptest2/pom.xml is not upgraded to 
latest versions.
Is this a miss? Or the change is not needed?

Regards,
Ram

Any best practices for hive upgrade from 1.2.1 to 3.1.2

[Battula, Brahma Reddy]

Hi All,

We are planning to upgrade the hive from 1.2.1 to 3.1.2, can we get any best 
practices ..?

Is any chance to upgrade without down time (if we disable new features like 
managed tables)..?


Thanks.