Re: [EXTERNAL] Re: [ANNOUNCE] Apache Hive 4.0.0 Released

[Pravin sinha]

Thanks for the update and the hard work to get it released, Denys.
Amazing to see Apache 4.0.0 released version out. Kudos to all the Hive
community members who contributed directly/indirectly to make this happen.

Best regards,
Pravin

On Tue, Apr 2, 2024, 6:15 PM Sankar Hariappan
 wrote:

> Absolutely exciting news! Congrats to the entire Hive community for making
> this release happen!
>
> -Sankar
>
> From: Pau Tallada 
> Sent: Tuesday, April 2, 2024 2:31 PM
> To: u...@hive.apache.org
> Cc: dev@hive.apache.org
> Subject: [EXTERNAL] Re: [ANNOUNCE] Apache Hive 4.0.0 Released
>
> You don't often get email from tall...@pic.es.
> Learn why this is important
> Congrats to all for the hard work
>
> Missatge de Butao Zhang mailto:butaozha...@163.com>>
> del dia dt., 2 d’abr. 2024 a les 10:58:
> I'm thrilled to see the official release of Apache Hive 4.0.0, marking
> another milestone in the development of the Hive community. I want to
> extend my gratitude to all the partners in the community for their hard
> work.
> Also special thanks to Denys for your diligent code reviews and efforts in
> completing the version release process, which I deeply admire.
>
> Wishing the Apache Hive community continued growth and success. Keep up
> the great work!
>
>
> Thanks,
> Butao Zhang
>
>
>  Replied Message 
> From
> Stamatis Zampetakis
> Date
> 4/2/2024 16:39
> To
> 
> Cc
> u...@hive.apache.org
> Subject
> Re: [ANNOUNCE] Apache Hive 4.0.0 Released
> The new Apache Hive 4.0.0 release brings roughly 5K new commits (since
> Apache Hive 3.1.3) and it's probably the biggest release so far in the
> history of the project. The numbers clearly show that this is a
> collective effort that wouldn't be possible without a strong community
> and many volunteers along the years. Many thanks to everyone involved!
>
> A special mention to Denys who went above and beyond his role of
> release manager triaging release blockers, reviewing and fixing many
> of those tickets that were blocking us for the past few months.
>
> Best,
> Stamatis
>
> On Sun, Mar 31, 2024 at 2:54 PM Battula, Brahma Reddy
> mailto:bbatt...@visa.com.invalid>> wrote:
>
> 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 mailto:dkuzme...@apache.org>>
> Date: Saturday, March 30, 2024 at 00:07
> To: u...@hive.apache.org <
> u...@hive.apache.org>, dev@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
>
>
> --
> --
> Pau Tallada Crespí
> Departament de Serveis
> Port d'Informació Científica (PIC)
> Tel: +34 93 170 2729
> --
>
>

Re: Release of Hive 4 and TPC-DS benchmark

[Pravin sinha]

Thanks for the update on this, Denys. Do we have any tracking jira for the
plan on performance test on the branch-4 build and is that the only
activity pending for releasing Hive-4.0.0?

Regards,
Pravin

On Fri, Mar 1, 2024 at 7:03 PM Denys Kuzmenko
 wrote:

> Hi All,
>
> Some updates on Hive-4.0 status:
>
> All known 4.0 release blockers were addressed and merged to the master.
> Thanks to everyone involved!!!
> We've raised a new PR to rebase branch-4.0. After that, we'll accept only
> bug fixes or some major improvements.
>
> Feel free to check and test branch-4.0 in a couple of days. We'll continue
> running number of functional & performance tests before the RC.
>
> Regards,
> Denys
>
> On Tue, Jan 30, 2024 at 6:40 AM Okumin  wrote:
>
> > Hi,
> >
> > We deployed a test version of Hive 4 in our production. It is mostly
> > working well. I appreciate the community's effort.
> >
> > Let me bump this thread so that community members can share the latest
> > situation, and we can contribute to the remaining problems.
> >
> > Currently, we list the following tickets labeled with hive-4.0.0-must[1].
> > - HIVE-27858: OOM happens when selecting many columns and JOIN
> > - HIVE-26654: Test with the TPC-DS benchmark
> > - HIVE-24167: No.14 (Postponed until 4.1.0)
> > - HIVE-26986: No.71 (No labels)
> >
> > We have already applied a workaround[2] for HIVE-24167. Also, Denys
> > says HIVE-26986 is not a blocker of Hive 4.0.0. So, I expect
> > HIVE-27858 to be the only blocker.
> >
> > I have some proposals about the next action.
> > - Can we take over HIVE-27858? We are the reporter of the ticket. It
> > would be reasonable If Naveen is not working on it yet
> > - We may review HIVE-27984[3]. As I mentioned in another thread[4], it
> > would have a fairly big impact on the Hive ecosystem
> >
> > And I would like someone to take a look at the following PR for
> > HIVE-24167. It is not a blocker thanks to
> > `hive.optimize.cte.materialize.threshold=-1`. However, we plan to use
> > Hive 4 with CTE materialization.
> > https://github.com/apache/hive/pull/5037
> >
> > Thanks!
> >
> > - [1]
> >
> https://issues.apache.org/jira/issues/?jql=labels%20%3D%20hive-4.0.0-must
> > - [2] https://github.com/apache/hive/pull/4858
> > - [3] https://github.com/apache/hive/pull/4984
> > - [4] https://www.mail-archive.com/dev@hive.apache.org/msg144280.html
> >
> > Regards,
> > Okumin
> >
> > On Thu, Nov 23, 2023 at 11:42 PM Butao Zhang 
> wrote:
> > >
> > > Cool! Thank you Denys for driving this!
> > >
> > >
> > > Thanks,
> > > Butao Zhang
> > >  Replied Message 
> > > | From | Attila Turoczy |
> > > | Date | 11/23/2023 22:29 |
> > > | To |  |
> > > | Subject | Re: Release of Hive 4 and TPC-DS benchmark |
> > > Excellent new Denys! Hive 4 is here! Can't wait :)
> > >
> > > -Attila
> > >
> > >
> > > On Thu, Nov 23, 2023 at 3:20 PM Denys Kuzmenko 
> > wrote:
> > >
> > > Update:
> > > 1. Query 2, 71: Resolved in HIVE-27006 [1];
> > >
> > > 2. Query 97: Under review in HIVE-27269 [2];
> > > Thanks, Seonggon for providing a reproduce qfile.
> > >
> > > 3. Query 14: Reported in HIVE-24167 [3];
> > > set hive.optimize.cte.materialize.threshold to -1 by default in Hive 4
> > and
> > > fix it in the next versions
> > >
> > > 4. HIVE-26986 [4] is a performance improvement that is nice to have,
> but
> > > not a blocker for the release.
> > >
> > > Be advised, next week we plan to cut 4.0.0 release branch from master
> and
> > > start testing.
> > >
> > > Thanks, Denys
> > >
> > > [1] https://issues.apache.org/jira/browse/HIVE-27006
> > > [2] https://issues.apache.org/jira/browse/HIVE-27269
> > > [3] https://issues.apache.org/jira/browse/HIVE-24167
> > > [4] https://issues.apache.org/jira/browse/HIVE-26986
> > >
> > >
> >
>

Re: Fix Version is now mandatory in Jira

[Pravin sinha]

Hi Ayush

Thanks for the update. Given that the branch for 4.0.0 is cut, for
resolving jira in master branch what is the "fix version" decided to be
given? Do we already have a place-holder created for the version next to
4.0.0?
 Asking this anticipating that not everything from master will be cherry
picked to branch-4.0 .

Thanks,
Pravin

On Thu, Nov 23, 2023 at 8:00 PM Ayush Saxena  wrote:

> Hi All,
> Following INFRA-24974, now for any Hive ticket, it is mandatory to
> provide the Fix Version, if not it won't let you resolve the ticket.
>
> Fix Version is a mandatory column which is used to populate the
> release notes, So, please put the correct fix version while resolving
> the tickets.
>
> If you aren't sure, just check the POM for the hive version in the
> branch where the code was merged.
>
> Let me know if there are any issues. In case the code isn't merged to
> any of the release branches, or if it is an Invalid or Dupe ticket,
> please add Not Applicable as the fix version & resolve.
>
> PS. If you want to give it a try, can try on
> https://issues.apache.org/jira/browse/HIVE-27909, I created that to
> try myself :-)
>
> -Ayush
>

Re: [ANNOUNCE] New PMC Member: Ayush Saxena

[Pravin Sinha]

Congratulations, Ayush ! Well deserved.

-Pravin

On Wed, Dec 21, 2022 at 10:18 AM Kirti Ruge  wrote:

> Congratulations Ayush.
>
> On Wed, 21 Dec 2022 at 12:15 AM, Chris Nauroth 
> wrote:
>
>> Congratulations, Ayush!
>>
>> Chris Nauroth
>>
>>
>> On Tue, Dec 20, 2022 at 10:02 AM Sai Hemanth Gantasala <
>> saihema...@cloudera.com> wrote:
>>
>> > Congratulations Ayush, Very well deserved!!.
>> >
>> > On Mon, Dec 19, 2022 at 5:12 PM Naveen Gangam 
>> > wrote:
>> >
>> >> Hello Hive Community,
>> >> Apache Hive PMC is pleased to announce that Ayush Saxena has accepted
>> the
>> >> Apache Hive PMC's invitation to become PMC Member, and is now our
>> newest
>> >> PMC member. Many thanks to Ayush for all the contributions he has made
>> and
>> >> looking forward to many more future contributions in the expanded role.
>> >>
>> >> Please join me in congratulating Ayush !!!
>> >>
>> >> Cheers,
>> >> Naveen (on behalf of Hive PMC)
>> >>
>> >>
>> >
>>
>

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

[Pravin Sinha]

Hi Aman,
 I also think that we can merge the PR to enable the test pipeline if the
change looks fine and subsequently we can fix the tests to bring it to
green state (hopefully by cherry picking a few commits from branch-3.1
which is already in green state) . Looks like currently the tests are
broken in branch-3.

Thanks,
Pravin

On Thu, Dec 8, 2022 at 3:59 PM Aman Raj 
wrote:

> Hi team,
>
> For the addition of Jenkins file for branch-3, branch-3 has some existing
> tests failing which was because Jenkins was not running on branch-3. We are
> planning to merge this Jenkins file irrespective of this PR having test
> failures, since this does not change the code. We will create separate
> tasks for ensuring that branch-3 has a green build.
>
> Link to the PR : https://github.com/apache/hive/pull/3841
>
> Fyi, branch-3.1 has a green build.
>
> Thanks,
> Aman.
> 
> From: Aman Raj 
> Sent: Wednesday, December 7, 2022 3:19 PM
> To: dev@hive.apache.org 
> Subject: Re: [EXTERNAL] Re: Sync of Branch-3 & Branch-3.1 for 3.2.0
> pipeline
>
> 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%7C4beeb2a178774ae320db08dad8386d36%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060034129929499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=29%2BOXXGM%2BuArowRGRO8gHtE6L8axnnlchKCMrE0H22Q%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%7C4beeb2a178774ae320db08dad8386d36%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060034129929499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=h2clHBrW3CxgjDTEL1QJDx6fSSai3OOFg5Q9DclVd6c%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%7C4beeb2a178774ae320db08dad8386d36%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060034129929499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=6QXqEJmGGSdac7I1K4XE6fSLiILpY1PbV2W1mZKdG7g%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-
> >>> 

Re: [EXTERNAL] Re: Proposal : New Release 3.2.0 | Fixing CVE's and Bugs on apache hive branch-3

[Pravin Sinha]

+1,

Thanks for driving this, Aman. Apart from CVE fixes, do you have a list of
JIRAs to be targeted?

-Pravin

On Thu, Nov 3, 2022 at 11:12 PM Chris Nauroth  wrote:

> Thank you for driving this!
>
> To kick things off, I have filed HIVE-26702 for a backport of HIVE-17315 (a
> total of 5 sub-tasks/patches) to 3.2.0. This adds support for more flexible
> configuration of the metastore's database connection pooling. Dataproc's
> distribution has been running this in production backported onto release
> 3.1.3, so I can provide the patches.
>
> May I assume that our intent is to keep 3.2.x backward-compatible with
> 3.1.x?
>
> Chris Nauroth
>
>
> On Thu, Nov 3, 2022 at 3:53 AM Sankar Hariappan
>  wrote:
>
> > +1, I'm excited to see the scope includes important upgrades and CVE
> fixes.
> > We should carefully port the relevant patches from master as code has
> been
> > heavily refactored. But, it make perfect sense to give another 3.x
> release
> > from Hive to keep the users delighted.
> > Thanks Aman for the initiative!
> >
> > Thanks,
> > Sankar
> >
> > -Original Message-
> > From: 张铎(Duo Zhang) 
> > Sent: Thursday, November 3, 2022 2:53 PM
> > To: dev@hive.apache.org
> > Subject: [EXTERNAL] Re: Proposal : New Release 3.2.0 | Fixing CVE's and
> > Bugs on apache hive branch-3
> >
> > [You don't often get email from palomino...@gmail.com. Learn why this is
> > important at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > +1, and please include HIVE-24694...
> >
> > Thanks.
> >
> > Aman Raj  于2022年11月3日周四 17:03写道：
> > >
> > > Hi team,
> > >
> > >
> > > We know that Hive 4.0.0 release is ongoing but considering the number
> of
> > changes going into the release, it will take some iterations to come up
> > with the stable version for the same. Meanwhile there are a lot of issues
> > in Hive 3.1.3 which our customers have reported. In this scenario, it
> makes
> > sense to make a release from branch-3 which will have all the necessary
> > upgrades, bug and CVE fixes which are causing issues to the existing
> > customers. Also, Hive is still using Hadoop 3.1.0 whereas Spark 3.3 has
> > already moved to Hadoop 3.3.1. Therefore, we need to do the same for
> hive.
> > >
> > >
> > >
> > > I will be happy to take the ownership of this new release and will be
> > creating JIRA's for all the fixes that will go on with this release.
> > >
> > >
> > >
> > > Therefore, I am proposing a new release cut out from branch-3. The
> > release version would be hive-3.2.0.
> > >
> > >
> > >
> > > This version will include major upgrades as:
> > >
> > >   1.  Hadoop version upgrade to 3.3.4
> > >   2.  Zookeeper version upgrade to 3.6.3
> > >   3.  Tez version upgrade to 0.10.2
> > >   4.  Calcite version upgrade to 1.25.0
> > >   5.  Orc version upgrade to 1.6.9
> > >
> > > This version will also include major CVE fixes as follows:
> > >
> > >   1.  NVD - CVE-2020-13949 (nist.gov)<
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvd.nist.gov%2Fvuln%2Fdetail%2FCVE-2020-13949data=05%7C01%7CSankar.Hariappan%40microsoft.com%7C9a16a3a9d980415efe3308dabd7d0e80%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638030642105079238%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=8%2FAxIDkyXbP3KeRNFPEHXACUs65Hvn8Gu4pLiO%2FGKFM%3Dreserved=0
> >
> > - Libthrift Upgrade to 0.14.1 (OSS Jira :
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-25098data=05%7C01%7CSankar.Hariappan%40microsoft.com%7C9a16a3a9d980415efe3308dabd7d0e80%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638030642105079238%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=dr4H5nzlL5dVken7blGVIzkjnkA7%2BknJU7y5swp9Mxg%3Dreserved=0
> > <
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-25098data=05%7C01%7CSankar.Hariappan%40microsoft.com%7C9a16a3a9d980415efe3308dabd7d0e80%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638030642105079238%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=dr4H5nzlL5dVken7blGVIzkjnkA7%2BknJU7y5swp9Mxg%3Dreserved=0
> > >)
> > >
> > >   1.  NVD - CVE-2015-1832 (nist.gov)<
> >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvd.nist.gov%2Fvuln%2Fdetail%2FCVE-2015-1832data=05%7C01%7CSankar.Hariappan%40microsoft.com%7C9a16a3a9d980415efe3308dabd7d0e80%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638030642105079238%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=lVHLRdFRdjHkCNuO1IbY8xzUXEEiZYvWo%2FEi%2FWMCJus%3Dreserved=0
> >
> > - Derby upgrade to 10.14.2.0 (OSS Jira :
> >
> 

[jira] [Created] (HIVE-26383) OOM during join query

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-26383:
---

 Summary: OOM during join query
 Key: HIVE-26383
 URL: https://issues.apache.org/jira/browse/HIVE-26383
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha


{code:java}
[ERROR] 
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[innerjoin_cal_with_insert]
  Time elapsed: 100.73 s  <<< ERROR!
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.HashMap.newTreeNode(HashMap.java:1784)
at java.util.HashMap$TreeNode.putTreeVal(HashMap.java:2029)
at java.util.HashMap.putVal(HashMap.java:639)
at java.util.HashMap.put(HashMap.java:613)
at java.util.HashSet.add(HashSet.java:220)
at 
org.apache.hadoop.hive.ql.optimizer.calcite.stats.EstimateUniqueKeys.getUniqueKeys(EstimateUniqueKeys.java:229)
at 
org.apache.hadoop.hive.ql.optimizer.calcite.stats.EstimateUniqueKeys.getUniqueKeys(EstimateUniqueKeys.java:304)
at 
org.apache.hadoop.hive.ql.optimizer.calcite.stats.HiveRelMdRowCount.isKey(HiveRelMdRowCount.java:501)
at 
org.apache.hadoop.hive.ql.optimizer.calcite.stats.HiveRelMdRowCount.analyzeJoinForPKFK(HiveRelMdRowCount.java:302)
at 
org.apache.hadoop.hive.ql.optimizer.calcite.stats.HiveRelMdRowCount.getRowCount(HiveRelMdRowCount.java:102)
at GeneratedMetadataHandler_RowCount.getRowCount_$(Unknown Source)
at GeneratedMetadataHandler_RowCount.getRowCount(Unknown Source)
at 
org.apache.calcite.rel.metadata.RelMetadataQuery.getRowCount(RelMetadataQuery.java:212)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.swapInputs(LoptOptimizeJoinRule.java:1882)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.createJoinSubtree(LoptOptimizeJoinRule.java:1756)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.addToTop(LoptOptimizeJoinRule.java:1233)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.addFactorToTree(LoptOptimizeJoinRule.java:927)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.createOrdering(LoptOptimizeJoinRule.java:728)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.findBestOrderings(LoptOptimizeJoinRule.java:459)
at 
org.apache.calcite.rel.rules.LoptOptimizeJoinRule.onMatch(LoptOptimizeJoinRule.java:128)
at 
org.apache.calcite.plan.AbstractRelOptPlanner.fireRule(AbstractRelOptPlanner.java:333)
at org.apache.calcite.plan.hep.HepPlanner.applyRule(HepPlanner.java:542)
at 
org.apache.calcite.plan.hep.HepPlanner.applyRules(HepPlanner.java:407)
at 
org.apache.calcite.plan.hep.HepPlanner.executeInstruction(HepPlanner.java:243)
at 
org.apache.calcite.plan.hep.HepInstruction$RuleInstance.execute(HepInstruction.java:127)
at 
org.apache.calcite.plan.hep.HepPlanner.executeProgram(HepPlanner.java:202)
at 
org.apache.calcite.plan.hep.HepPlanner.findBestExp(HepPlanner.java:189)
at 
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.executeProgram(CalcitePlanner.java:2468)
at 
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.executeProgram(CalcitePlanner.java:2427)
at 
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.applyJoinOrderingTransform(CalcitePlanner.java:2193)
at 
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1750)
at 
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1605)
 {code}



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

Re: [ANNOUNCE] Denys Kuzmenko joins Hive PMC

[Pravin Sinha]

Congrats, Denys !

On Mon, Feb 7, 2022 at 11:02 PM aasha medhi 
wrote:

> Congratulations Denys !
>
> On Mon, Feb 7, 2022 at 10:36 PM Laszlo Pinter  >
> wrote:
>
> > Congrats Denys!
> >
> > On Mon, Feb 7, 2022, 6:00 PM László Bodor 
> > wrote:
> >
> > > Congrats Denys!!
> > >
> > > Naresh P R  ezt írta (időpont: 2022. febr.
> > 7.,
> > > H, 17:43):
> > >
> > > > Congrats Denys, well deserved !!!
> > > > ---
> > > > Regards,
> > > > Naresh P R
> > > >
> > > > On Mon, Feb 7, 2022 at 8:40 AM Ashutosh Chauhan <
> hashut...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I'm pleased to announce that Denys has accepted an invitation to
> > > > > join the Hive PMC. Denys has been a consistent and helpful
> > > > > figure in the Hive community for which we are very grateful. We
> > > > > look forward to the continued contributions and support.
> > > > >
> > > > > Please join me in congratulating Denys!
> > > > >
> > > > > Ashutosh (On behalf of Hive PMC)
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New committer: Ayush Saxena

[Pravin Sinha]

Congrats, Ayush !!
Well deserved. Keep up the good work.

~Pravin

On Mon, Feb 7, 2022 at 10:11 PM Battula, Brahma Reddy
 wrote:

> 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)
> >
>

[jira] [Created] (HIVE-25439) Make the DistCp stat csv content parse-able

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25439:
---

 Summary: Make the DistCp stat csv content parse-able
 Key: HIVE-25439
 URL: https://issues.apache.org/jira/browse/HIVE-25439
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha


The csv file generated by script replstats.sh isn't parse-able when the number 
of bytes Copied is huge. The 'Bytes Copied' field itself can have comma. E.g
{code:java}
#cat Repl#repl_testing20210802T153039308427#14711values.csv 

job_1624306668424_194169,2-Aug-2021 20:20:41,2-Aug-2021 20:22:08,1mins, 
27sec,2-Aug-2021 20:22:29,21sec,1,0,112,527,514,1,SUCCEEDED

{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-25355) EXPLAIN statement for write transactions with hive.txn.readonly.enabled fails

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25355:
---

 Summary: EXPLAIN statement for write transactions with 
hive.txn.readonly.enabled fails
 Key: HIVE-25355
 URL: https://issues.apache.org/jira/browse/HIVE-25355
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-25330) Make FS calls in CopyUtils retryable

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25330:
---

 Summary: Make FS calls in CopyUtils retryable
 Key: HIVE-25330
 URL: https://issues.apache.org/jira/browse/HIVE-25330
 Project: Hive
  Issue Type: Improvement
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-25305) Replayed transactions are not cleaned up properly on open txn timeout

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25305:
---

 Summary: Replayed transactions are not cleaned up properly on open 
txn timeout  
 Key: HIVE-25305
 URL: https://issues.apache.org/jira/browse/HIVE-25305
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-25272) READ transactions are getting logged in NOTIFICATION LOG

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25272:
---

 Summary: READ transactions are getting logged in NOTIFICATION LOG
 Key: HIVE-25272
 URL: https://issues.apache.org/jira/browse/HIVE-25272
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha


While READ transactions are already skipped from getting logged in NOTIFICATION 
logs, few are still getting logged. Need to skip those transactions as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-25164) Execute Bootstrap REPL load DDL tasks in parallel

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-25164:
---

 Summary: Execute Bootstrap REPL load DDL tasks in parallel
 Key: HIVE-25164
 URL: https://issues.apache.org/jira/browse/HIVE-25164
 Project: Hive
  Issue Type: Improvement
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24896) External table having same name as dropped managed table fails to replicate

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24896:
---

 Summary: External table having same name as dropped managed table 
fails to replicate
 Key: HIVE-24896
 URL: https://issues.apache.org/jira/browse/HIVE-24896
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24884) Move top level dump metadata content to be in JSON format

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24884:
---

 Summary: Move top level dump metadata content to be in JSON format
 Key: HIVE-24884
 URL: https://issues.apache.org/jira/browse/HIVE-24884
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


{color:#172b4d}The current content for _dumpmetadata file is TAB separated. 
This is not very flexible for extension. A more flexible format like JSON based 
content would be helpful for extending the content.{color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24733) Handle replication when db location and managed location is set to custom location on source

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24733:
---

 Summary: Handle replication when db location and managed location 
is set to custom location on source
 Key: HIVE-24733
 URL: https://issues.apache.org/jira/browse/HIVE-24733
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


{color:#172b4d} {color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24697) DbNotificationListener Cleaner thread dies with NoSuchMethodError

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24697:
---

 Summary: DbNotificationListener Cleaner thread dies with 
NoSuchMethodError
 Key: HIVE-24697
 URL: https://issues.apache.org/jira/browse/HIVE-24697
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha


{code:java}
java.lang.NoSuchMethodError: javax.jdo.Query.close()V
at 
org.apache.hadoop.hive.metastore.ObjectStore.doCleanNotificationEvents(ObjectStore.java:11025)
 
at 
org.apache.hadoop.hive.metastore.ObjectStore.cleanNotificationEvents(ObjectStore.java:10965)
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24654) Table level replication support for Atlas metadata

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24654:
---

 Summary: Table level replication support for Atlas metadata
 Key: HIVE-24654
 URL: https://issues.apache.org/jira/browse/HIVE-24654
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


Covers mainly Atlas export API payload change required to support table level 
replication



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24417) Add config options for Atlas client timeouts

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24417:
---

 Summary: Add config options for Atlas client timeouts
 Key: HIVE-24417
 URL: https://issues.apache.org/jira/browse/HIVE-24417
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24363) Current order of transactional event listeners is prone to deadlock in backend DB connections

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24363:
---

 Summary: Current order of transactional event listeners is prone 
to deadlock in backend DB connections
 Key: HIVE-24363
 URL: https://issues.apache.org/jira/browse/HIVE-24363
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha


Currently the AcidEventListener is added to the end of list transactional event 
listeners. When DbNotificationListener is configured in 
'hive.metastore.transactional.event.listeners'. The list will be formed as :

{"DbNotificationListener" , "AcidEventListener"} 

This will result in backend DB lock acquisition in this order:
{code:java}
 lock(a) {
// perform some op on a
    lock(b) {
  // perform some op on b
}
  }
{code}
On the other hand, there are some HMS API say for example commit_txn(), which 
calls the TxnHandler method directly, followed by DbNotificationListener 
processing. Which will result in the lock acquisition in reverse order:
{code:java}
lock(b) {
// perform some op on b    
lock(a) {
// perform some op on a
}   
 }
{code}
Note: 'a' and 'b' above are backend  DB lock and not a jvm lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24327) During Atlas metadata replication handle a case when AtlasServer entity not present

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24327:
---

 Summary: During Atlas metadata replication handle a case when 
AtlasServer entity not present 
 Key: HIVE-24327
 URL: https://issues.apache.org/jira/browse/HIVE-24327
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24267) RetryingClientTimeBased should perform first invocation immediately

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24267:
---

 Summary: RetryingClientTimeBased should perform first invocation 
immediately
 Key: HIVE-24267
 URL: https://issues.apache.org/jira/browse/HIVE-24267
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24244) NPE during Atlas metadata replication

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24244:
---

 Summary: NPE during Atlas metadata replication
 Key: HIVE-24244
 URL: https://issues.apache.org/jira/browse/HIVE-24244
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24187) Handle _files creation for HA config with same nameservice on source and destination

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24187:
---

 Summary: Handle _files creation for HA config with same 
nameservice on source and destination
 Key: HIVE-24187
 URL: https://issues.apache.org/jira/browse/HIVE-24187
 Project: Hive
  Issue Type: Improvement
Reporter: Pravin Sinha
Assignee: Pravin Sinha


Current HA is supported only for different nameservices on Source and 
Destination. We need to add support of same nameservice on Source and 
Destination.
Local nameservice will be passed correctly to the repl command.
Remote nameservice will be a random name and corresponding configs for the same.

Example:
Clusters originally configured with ns for hdfs:
src: ns1
target : ns1

We can denote remote name with some random name, say for example: nsRemote. 
This is how the command will see the ns w.r.t source and target:

Repl Dump : src: ns1, target: nsRemote
Repl Load: src: nsRemote, target: ns1

Entries in the _files(for managed table data loc) will be made with nsRemote in 
stead of ns1(for src).
Example: 
hdfs://nsRemote/whLoc/dbName.db/table1:checksum:subDir:hdfs://nsRemote/cmroot

Same way list of external table data locations will also be modified using 
nsRemote in stead of ns1(for src).

New configs can control the behavior:
*hive.repl.ha.datapath.replace.remote.nameservice = *
*hive.repl.ha.datapath.replace.remote.nameservice.name = *

Based on the above configs replacement of nameservice can be done.

This will also require that 'hive.repl.rootdir' is passed accordingly during 
dump and load:
Repl dump:
||Repl Operation||Repl Command||
|*Staging on source cluster*|
|Repl Dump|repl dump dbName with('hive.repl.rootdir'='hdfs://ns1/stagingLoc')|
|Repl Load|repl load dbName into dbName 
with('hive.repl.rootdir'='hdfs://nsRemote/stagingLoc')|
|*Staging on target cluster*|
|Repl Dump|repl dump dbName 
with('hive.repl.rootdir'='hdfs://nsRemote/stagingLoc')|
|Repl Load|repl load dbName into dbName 
with('hive.repl.rootdir'='hdfs://ns1/stagingLoc')|



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24170) Add the UDF jar explicitely to the classpath while handling drop function event during repl load.

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24170:
---

 Summary: Add the UDF jar explicitely to the classpath while 
handling drop function event during repl load.
 Key: HIVE-24170
 URL: https://issues.apache.org/jira/browse/HIVE-24170
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24148) TestHiveStrictManagedMigration.testExternalMove failing for all new PR.

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24148:
---

 Summary: TestHiveStrictManagedMigration.testExternalMove failing 
for all new PR.
 Key: HIVE-24148
 URL: https://issues.apache.org/jira/browse/HIVE-24148
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24131) Use original src location always when data copy runs on target

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24131:
---

 Summary: Use original src location always when data copy runs on 
target 
 Key: HIVE-24131
 URL: https://issues.apache.org/jira/browse/HIVE-24131
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24129) Deleting the previous successful dump directory should be based on config

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24129:
---

 Summary: Deleting the previous successful dump directory should be 
based on config
 Key: HIVE-24129
 URL: https://issues.apache.org/jira/browse/HIVE-24129
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Arko Sharma


{color:#22}Description: Provide a policy level config defaulted to 
true.{color}

{color:#22}This can help debug any issue in the production.{color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24114) Load is not working with both staging and data copy on target

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24114:
---

 Summary: Load is not working with both staging and data copy on 
target 
 Key: HIVE-24114
 URL: https://issues.apache.org/jira/browse/HIVE-24114
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24067) TestReplicationScenariosExclusiveReplica - Wrong FS error during DB drop

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24067:
---

 Summary: TestReplicationScenariosExclusiveReplica - Wrong FS error 
during DB drop
 Key: HIVE-24067
 URL: https://issues.apache.org/jira/browse/HIVE-24067
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


In TestReplicationScenariosExclusiveReplica during drop database operation for 
primary db, it leads to wrong FS error as the ReplChangeManager is associated 
with replica FS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-24011) Flaky test AsyncResponseHandlerTest

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-24011:
---

 Summary: Flaky test AsyncResponseHandlerTest
 Key: HIVE-24011
 URL: https://issues.apache.org/jira/browse/HIVE-24011
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha


[http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1352/2/tests/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23960) Partition with no column statistics leads to unbalanced calls to openTransaction/commitTransaction error during get_partitions_by_names

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23960:
---

 Summary: Partition with no column statistics leads to unbalanced 
calls to openTransaction/commitTransaction error during get_partitions_by_names
 Key: HIVE-23960
 URL: https://issues.apache.org/jira/browse/HIVE-23960
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


{color:#172b4d}Creating a partition with data and adding another partition is 
leading to unbalanced calls to open/commit transaction during 
get_partitions_by_names call.
{color}

{color:#172b4d}Issue was discovered during REPL DUMP operation which uses  this 
HMS call to get the metadata of partition. This error occurs when there is a 
partition with no column statistics.{color}

{color:#172b4d}To reproduce:{color}
{code:java}
CREATE TABLE student_part_acid(name string, age int, gpa double) PARTITIONED BY 
(ds string) STORED AS orc;
LOAD DATA INPATH ‘/user/hive/partDir/student_part_acid/ds=20110924’ INTO TABLE 
student_part_acid partition(ds=20110924);
ALTER TABLE student_part_acid ADD PARTITION (ds=20110925);

Now we try to preform REPL DUMP it fails with this the error "Unbalanced calls 
to open/commit transaction" on the HS2 side. 
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23916) Fix Atlas client dependencies version

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23916:
---

 Summary: Fix Atlas client dependencies version
 Key: HIVE-23916
 URL: https://issues.apache.org/jira/browse/HIVE-23916
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23835) Repl Dump should dump function binaries to staging directory

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23835:
---

 Summary: Repl Dump should dump function binaries to staging 
directory
 Key: HIVE-23835
 URL: https://issues.apache.org/jira/browse/HIVE-23835
 Project: Hive
  Issue Type: Task
Reporter: Pravin Sinha
Assignee: Pravin Sinha


{color:#172b4d}When hive function's binaries are on source HDFS, repl dump 
should dump it to the staging location in order to break cross clusters 
visibility requirement.{color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23611) Mandate fully qualified absolute path for for external table base dir during REPL operation

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23611:
---

 Summary: Mandate fully qualified absolute path for for external 
table base dir during REPL operation
 Key: HIVE-23611
 URL: https://issues.apache.org/jira/browse/HIVE-23611
 Project: Hive
  Issue Type: Improvement
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23605) Wrong FS error during _external_tables_info creation when staging location is remote

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23605:
---

 Summary: Wrong FS error during _external_tables_info creation when 
staging location is remote
 Key: HIVE-23605
 URL: https://issues.apache.org/jira/browse/HIVE-23605
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: Pravin Sinha


When staging location is on target cluster, Repl Dump fails to create 
_external_tables_info file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23539) Optimize data copy during repl load operation for HDFS based staging location

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23539:
---

 Summary: Optimize data copy during repl load operation for HDFS 
based staging location
 Key: HIVE-23539
 URL: https://issues.apache.org/jira/browse/HIVE-23539
 Project: Hive
  Issue Type: Improvement
Reporter: Pravin Sinha
Assignee: Pravin Sinha






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HIVE-23538) Cannot run setBugDatabaseInfo from findbugs during preCommit

[Pravin Sinha (Jira)]

Pravin Sinha created HIVE-23538:
---

 Summary: Cannot run setBugDatabaseInfo from findbugs during 
preCommit
 Key: HIVE-23538
 URL: https://issues.apache.org/jira/browse/HIVE-23538
 Project: Hive
  Issue Type: Bug
Reporter: Pravin Sinha
Assignee: David Mollitor


During  the preCommit of the patch HIVE-23353 this is seen.
-1  findbugs1m 5s   patch/common cannot run setBugDatabaseInfo from 
findbugs
-1  findbugs10m 27s patch/ql cannot run setBugDatabaseInfo 
from findbugs
-1  findbugs1m 51s  patch/itests/hive-unit cannot run 
setBugDatabaseInfo from findbugs



--
This message was sent by Atlassian Jira
(v8.3.4#803005)