The release date of Hive v3.1.4

Hi team, Recently I have been working on SPARK-44114, in which we attempt to bump Spark's Hive deps into v3.x, however during the testing phase, we discovered the issue of HIVE-27508 and this seems to be the blocker of our adoption. By looking at the GitHub MR, the fix itself seems to have

"\n" in HiveConf

Hey All! Maybe I'm missing some history here: does anyone know why and for what we use line break characters in the descriptions in HiveConf ? (1046 occurrences as we speak) As far as I can tell

Re: Force coding style in hive precommit

Thanks, guys, I created https://issues.apache.org/jira/browse/HIVE-28072 I believe we all agree to introduce style checking to at least try to avoid further issues and how or whether to force it is a different question, feel free to follow HIVE-28072 Regards, Laszlo Bodor Zoltán Rátkai ezt

Re: Enhance PerfLogger with annotations using AOP

Hey Soumyakanti, Thanks for starting this discussion. I like the idea of reducing boilerplate code and one way although not the only one is using AOP. AOP libraries rely on code injection and there are various pros/cons [1] when using such tools. If AspectJ is the best option for this use-case I

Enhance PerfLogger with annotations using AOP

Hi all, Do you guys think it's a good idea to implement annotations for PerfLogger? Currently, we have to surround the code with a PerfLogBegin and a PerfLogEnd to log execution time. There are many methods where the first and last line are these. Instead, we could use AOP to create an annotation

Community over Code EU 2024 Travel Assistance Applications now open!

Hello to all users, contributors and Committers! The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for Community over Code EU 2024 are now open! We will be supporting Community over Code EU, Bratislava, Slovakia, June 3th - 5th, 2024. TAC exists

Re: Subscribe to security ML (Hive Committers)

Hey Sankar, I don't think we can add you explicitly. You have to submit the subscription request from your @apache domain following the traditional procedure. Best, Stamatis On Fri, Feb 2, 2024 at 9:31 AM Sankar Hariappan wrote: > > Hi Stamatis/Ayush, > Could you please add me to the security

Re: Subscribe to security ML (Hive Committers)

Hi Stamatis/Ayush, Could you please add me to the security mailing list of Hive? sank...@apache.org Thanks, Sankar On 2024/01/22 13:53:53 Stamatis Zampetakis wrote: > For traceability purposes, please subscribe to the mailing list with > your @apache.org address. Any other requests will be

Re: Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

Thanx everyone for voting. If I count right, we have 13 +1 votes (8 binding) & no vetoes. The vote passes. I will shoot an announcement in a couple of days and update the website to reflect the decision -Ayush On Fri, 19 Jan 2024 at 18:19, Krisztian Kasa wrote: > +1 > > On Fri, Jan 19, 2024

Hive jdbc connector

Hi sir, Which Java version does hive jdbc connector supports? Thanks, Vijay S.

Re: Release of Hive 4 and TPC-DS benchmark

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

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

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

Re: [Discuss] Enable Attachments for Hive mailing lists

+1

Re: [Discuss] Enable Attachments for Hive mailing lists

+1 from me. It would be nice if we could attach design docs to the mail thread. Thanks! Simhadri G On Tue, Jan 23, 2024 at 1:40 PM Stamatis Zampetakis wrote: > +0 > > I rarely open attachments from public mailing lists for security > reasons (unless we are talking for known safe extensions).

TABLESAMPLE with buckets not working, it does not prune input

Hi all, We have a web platform in production[1] that uses Hive to facilitate access to massive cosmological datasets. When launched in 2016 over Hive 2.1.2 we used the TABLESAMPLE clause on clustered tables to allow quick subsampling of the data. However, we have been unable to get the same

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Hey All, Thank you Alessandro and Stamatis for the suggestion to cool off. I think I was seeing the state and the messages at the wrong time - and was writing a message light headed; I should have seen the step forward...or at least have taken a break before hitting reply Ayush: sorry for

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Hey guys, I advise you to take Stamatis' suggestion and cool it off for a bit, this is getting personal and you know it's only counterproductive. Having worked with both of you, I know you have always done everything in the best interest of the project and always acted in good faith, no reason to

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Ok Zoltan, you are always right, but listening to other people sometimes doesn't hurt, maybe even if they aren't as smart as you (like me & everyone you consider not so smart like you). Let me ask something: * If something breaks like code or something like that? What do you do? Humiliate or

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

On 1/23/24 10:10, Ayush Saxena wrote: Ok I will get the repo deleted. I am not taking any sarcastic comments from Zoltan at this stage. Believe me I am not getting anything for having my name there. Why I did this? Someone was so obsessed with getting his name checked into the "Apache Code"

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Hey team, Initially we had zero people willing to help and advance this topic. Now we have more than three and I am sure everyone has good intentions. Let's not forget that in Apache the community is more important than code. If we have a healthy community we can fix any kind of problem in the

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Ok I will get the repo deleted. I am not taking any sarcastic comments from Zoltan at this stage. Believe me I am not getting anything for having my name there. Why I did this? Someone was so obsessed with getting his name checked into the "Apache Code" that he developed something on his fork &

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

I was thinking of pushing the current state of Zoltan's branch to the new apache remote. I did this just now in https://github.com/apache/hive-dev-box/tree/main branch. I can cherry-pick the remaining commits from master and drop that branch unless we have other things to consider as well. Please

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

> I just copied the repo: cp -R and Put Zoltan's name & reference to his > repo. I didn't knew any better way than that, you can definitely force push > with another fancy approach lol...what a sophisticated approach - I wonder if you don't know the `fancy approach` then why you've done it? I

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

I just copied the repo: cp -R and Put Zoltan's name & reference to his repo. I didn't knew any better way than that, you can definitely force push with another fancy approach, just c-pick the other commits for NOTICE & all on top of it. The old code & commits had some cloudera references, which I

Re: [Discuss] Enable Attachments for Hive mailing lists

+0 I rarely open attachments from public mailing lists for security reasons (unless we are talking for known safe extensions). Moreover, I find it easier to glance through code if people share a link to a PR or code in GitHub than if I have to download and apply a patch locally. I understand

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

Thanks for helping advance this Ayush! I saw that the commit history was not retained. Is there any reason for dropping it? Keeping the history and the people who contributed thus far would be nice to have. For the contribution model to this repository, I would recommend the usual process. Raise

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

This is the new repo: https://github.com/apache/hive-dev-box It has the initial code from Zoltan, LICENSE, NOTICE & Disclaimer-WIP file + I added Apache Header to all the files wherever possible. We need a docker space to push these built images, have requested INFRA for the same. The repo is in

Re: [DISCUSS] Migrate precommit git repos from kgyrtkirk to apache

I think we are now not using Zoltan's repo. We are using a fork from a contributor in the hive code.[1], I will go ahead and create a repo under Apache Hive for hive-dev-box tomorrow & put the LICENSE, NOTICE & DISCLAIMER-WIP files in it, Then will take things from there, atleast it would be a

Re: Subscribe to security ML (Hive Committers)

For traceability purposes, please subscribe to the mailing list with your @apache.org address. Any other requests will be denied from now onwards. The moderators (us) have no way to tell if the request comes from a valid Hive community member or a malicious attacker. On Mon, Jan 22, 2024 at 11:16 

Re: [Discuss] Enable Attachments for Hive mailing lists

+1 for me as well. We need it. -Attila On Mon, Jan 22, 2024 at 1:25 PM Ayush Saxena wrote: > Hi All, > As of now we don't allow having attachments on the hive mailing lists > (apart from security ML), This prevents us from attaching patches/design > doc or even screenshots of issues being

[Discuss] Enable Attachments for Hive mailing lists

Hi All, As of now we don't allow having attachments on the hive mailing lists (apart from security ML), This prevents us from attaching patches/design doc or even screenshots of issues being reported on our mailing lists. A lot of projects allow that, I feel we should enable this for our Hive

Re: Re: Cleanup remote feature/wip branches

Cleanup is complete. Thanks to Krisztian and Zhihua for helping out! I only kept https://github.com/apache/hive/tree/release-1.1 cause I was unsure of its purpose. Best, Stamatis On Fri, Jan 19, 2024 at 6:46 PM Chao Sun wrote: > > +1 > > On Fri, Jan 19, 2024 at 4:33 AM Attila Turoczy > wrote:

Re: Subscribe to security ML (Hive Committers)

The security issues are of utmost importance to ASF projects and should be treated in a timely manner. Thanks Ayush for the reminder! Best, Stamatis On Mon, Jan 22, 2024 at 11:05 AM Ayush Saxena wrote: > > Hi Folks, > In case any of the committers or PMC members are not subscribed to the >

Subscribe to security ML (Hive Committers)

Hi Folks, In case any of the committers or PMC members are not subscribed to the security mailing list, please subscribe & help address or share pointers if you can. if you are a committer, please send a mail to: security-subscr...@hive.apache.org This mail list is moderated, so the request

Re: Consultation on the future support plan for Hive on Spark

Hi YiFeng Thanks for reaching out, I think there is a mail which may be helpful for you: https://lists.apache.org/thread/vsqgjyots3dqjtkzzdbxxgrwg34cnqlc On Fri, Jan 19, 2024 at 3:55 PM 陆一峰 wrote: > Hi, Hive Team > We are from the bytedance EMR >

Re: Re: Cleanup remote feature/wip branches

+1 On Fri, Jan 19, 2024 at 4:33 AM Attila Turoczy wrote: > > +1 > > On Fri, 19 Jan 2024 at 04:30, dengzhhu653 wrote: > > > +1 > > At 2024-01-19 19:58:49, "Krisztian Kasa" > > wrote: > > >+1 > > > > > >On Fri, Jan 19, 2024 at 11:28 AM Alessandro Solimando < > > >alessandro.solima...@gmail.com>

Re: Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 On Fri, Jan 19, 2024 at 1:33 PM dengzhhu653 wrote: > +1 (non-binding)Best,Zhihua > At 2024-01-17 17:07:01, "László Bodor" wrote: > >+1 (binding) > > > >Sankar Hariappan ezt írta > >(időpont: 2024. jan. 17., Sze, 10:05): > > > >> +1 > >> > >> -Sankar > >> > >> -Original Message- >

Re:Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (non-binding)Best,Zhihua At 2024-01-17 17:07:01, "László Bodor" wrote: >+1 (binding) > >Sankar Hariappan ezt írta >(időpont: 2024. jan. 17., Sze, 10:05): > >> +1 >> >> -Sankar >> >> -Original Message- >> From: Stamatis Zampetakis >> Sent: Wednesday, January 17, 2024 1:56 PM >> To:

Re: Re: Cleanup remote feature/wip branches

+1 On Fri, 19 Jan 2024 at 04:30, dengzhhu653 wrote: > +1 > At 2024-01-19 19:58:49, "Krisztian Kasa" > wrote: > >+1 > > > >On Fri, Jan 19, 2024 at 11:28 AM Alessandro Solimando < > >alessandro.solima...@gmail.com> wrote: > > > >> +1, thanks Stamatis > >> > >> On Fri, Jan 19, 2024, 11:14 Ayush

Re:Re: Cleanup remote feature/wip branches

+1 At 2024-01-19 19:58:49, "Krisztian Kasa" wrote: >+1 > >On Fri, Jan 19, 2024 at 11:28 AM Alessandro Solimando < >alessandro.solima...@gmail.com> wrote: > >> +1, thanks Stamatis >> >> On Fri, Jan 19, 2024, 11:14 Ayush Saxena wrote: >> >> > +1 >> > >> > -Ayush >> > >> > > On 19-Jan-2024, at 3:41 

Re: Cleanup remote feature/wip branches

+1 On Fri, Jan 19, 2024 at 11:28 AM Alessandro Solimando < alessandro.solima...@gmail.com> wrote: > +1, thanks Stamatis > > On Fri, Jan 19, 2024, 11:14 Ayush Saxena wrote: > > > +1 > > > > -Ayush > > > > > On 19-Jan-2024, at 3:41 PM, Stamatis Zampetakis > > wrote: > > > > > > Hey everyone, >

Re: Cleanup remote feature/wip branches

+1, thanks Stamatis On Fri, Jan 19, 2024, 11:14 Ayush Saxena wrote: > +1 > > -Ayush > > > On 19-Jan-2024, at 3:41 PM, Stamatis Zampetakis > wrote: > > > > Hey everyone, > > > > I noticed that in our official git repo [1] we have some kind of > > feature/WIP branches (see list below). Most of

Re: Cleanup remote feature/wip branches

+1 -Ayush > On 19-Jan-2024, at 3:41 PM, Stamatis Zampetakis wrote: > > Hey everyone, > > I noticed that in our official git repo [1] we have some kind of > feature/WIP branches (see list below). Most of them (if not all) are > stale, add noise, and some of them eat CI resources (storage and

Cleanup remote feature/wip branches

Hey everyone, I noticed that in our official git repo [1] we have some kind of feature/WIP branches (see list below). Most of them (if not all) are stale, add noise, and some of them eat CI resources (storage and CPU) since Jenkins picks them up for builds/precommits. I would like to drop those

CI is down: No space left on device

FYI: https://issues.apache.org/jira/browse/HIVE-28013 Best, Stamatis

Consultation on the future support plan for Hive on Spark

Hi, Hive Team We are from the bytedance EMR team，and we have noticed that the Hive community recently removed support for Hive on Spark https://issues.apache.org/jira/browse/HIVE-26134 We would like to inquire whether the Hive community has explicitly

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 On Wed, Jan 17, 2024 at 3:48 PM Larry Z. wrote: > +1 (binding) > > On Wed, Jan 17, 2024 at 9:46 AM Chao Sun wrote: > > > +1 (binding) > > > > On Wed, Jan 17, 2024 at 1:24 AM Alessandro Solimando > > wrote: > > > > > > +1 (non binding) > > > > > > On Wed, 17 Jan 2024 at 10:23, Denys

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (binding) On Wed, Jan 17, 2024 at 9:46 AM Chao Sun wrote: > +1 (binding) > > On Wed, Jan 17, 2024 at 1:24 AM Alessandro Solimando > wrote: > > > > +1 (non binding) > > > > On Wed, 17 Jan 2024 at 10:23, Denys Kuzmenko > wrote: > > > > > +1 (binding) > > > > -- Xuefu Zhang "In Honey We

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

Hi Ayush, I'm working on the last few commits to backport to the branch. Hopefully within 1-2 months I can start the release process. Our goal is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this year. Chao On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena wrote: > > Thanx

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (binding) On Wed, Jan 17, 2024 at 1:24 AM Alessandro Solimando wrote: > > +1 (non binding) > > On Wed, 17 Jan 2024 at 10:23, Denys Kuzmenko wrote: > > > +1 (binding) > >

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (non binding) On Wed, 17 Jan 2024 at 10:23, Denys Kuzmenko wrote: > +1 (binding) >

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (binding)

Re: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 (binding) Sankar Hariappan ezt írta (időpont: 2024. jan. 17., Sze, 10:05): > +1 > > -Sankar > > -Original Message- > From: Stamatis Zampetakis > Sent: Wednesday, January 17, 2024 1:56 PM > To: dev@hive.apache.org > Subject: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL > > +1 (binding) >

RE: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL

+1 -Sankar -Original Message- From: Stamatis Zampetakis Sent: Wednesday, January 17, 2024 1:56 PM To: dev@hive.apache.org Subject: [EXTERNAL] Re: [VOTE] Mark Hive 1.x EOL +1 (binding) Best, Stamatis On Wed, Jan 17, 2024 at 8:21 AM Attila Turoczy wrote: > > +1 > > -Attila > > On

Re: SonarCloud deprecates Java11?

Hi Stamatis, Thank you for the information. I didn't know about that. Zsolt Stamatis Zampetakis ezt írta (időpont: 2024. jan. 16., K, 22:06): > Hello, > > There is a PR for addressing the problem [1] and it will be merged in > the next few days. In the meantime feel free to ignore the Sonar >

Re: [VOTE] Mark Hive 1.x EOL

+1 (binding) Best, Stamatis On Wed, Jan 17, 2024 at 8:21 AM Attila Turoczy wrote: > > +1 > > -Attila > > On Tue, 16 Jan 2024 at 22:18, Butao Zhang wrote: > > > +1 > > > > > > > > Thanks, > > Butao Zhang > > Replied Message > > | From | Ayush Saxena | > > | Date | 1/17/2024 14:15 | >

Re: [VOTE] Mark Hive 1.x EOL

+1 -Attila On Tue, 16 Jan 2024 at 22:18, Butao Zhang wrote: > +1 > > > > Thanks, > Butao Zhang > Replied Message > | From | Ayush Saxena | > | Date | 1/17/2024 14:15 | > | To | dev | > | Subject | [VOTE] Mark Hive 1.x EOL | > Hi All, > Following the discussion in [1], Starting an

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

Thanx everyone for the feedback, I have started a formal thread to mark 1.x EOL. We can have one last release for 2.x as Chao mentioned, with some required changes + our CVE's & get the release line marked as EOL then. @Chao Sun Do let us know if you have a proposed timeline for that. -Ayush

Re: [VOTE] Mark Hive 1.x EOL

+1 Thanks, Butao Zhang Replied Message | From | Ayush Saxena | | Date | 1/17/2024 14:15 | | To | dev | | Subject | [VOTE] Mark Hive 1.x EOL | Hi All, Following the discussion in [1], Starting an official thread to mark Hive 1.x EOL. Marking a release line EOL, means there won't be

[VOTE] Mark Hive 1.x EOL

Hi All, Following the discussion in [1], Starting an official thread to mark Hive 1.x EOL. Marking a release line EOL, means there won't be any further releases for that release line. I will start with my +1 -Ayush [1] https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s

Re: [EXTERNAL] Re: [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x

Thanx Everyone for the feedback. I have created https://issues.apache.org/jira/browse/HIVE-28005 for the removal of this module from master branch. -Ayush On Wed, 10 Jan 2024 at 21:42, Sankar Hariappan wrote: > +1, It is needed only for upgrading from Hive 1.x/2.x to 3.x and not > relevant for

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

I was confused about the subject line since it says 3.x as well along with 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or just 1.x and 2.x? I think it makes sense to EOL 1.x. Looks like 2.x is still being maintained by Chao and I think we were backporting PRs to the 3.x line

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

Dear PMC's, Do we have a verdict / decision about this? -Attila On Wed, Jan 10, 2024 at 5:45 PM Chao Sun wrote: > On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 2.3 > branch is being actively maintained so far). Hopefully this will be > the last release in the branch-2

Re: SonarCloud deprecates Java11?

Hello, There is a PR for addressing the problem [1] and it will be merged in the next few days. In the meantime feel free to ignore the Sonar errors; nothing too bad will happen by doing this. Many thanks to Wechar Yu for jumping on this and pushing it forward. Best, Stamatis [1]

SonarCloud deprecates Java11?

Hi, I saw that in one of the splits at my pr. Should we start to worry? jenkins / hive-precommit / PR-4740 / #22 (apache.org) [2024-01-16T19:33:27.462Z] [INFO] BUILD FAILURE

Re: review help

Hi gaoxiong, Thanks for you contribution! I left several minor comments, please take a look. Thanks, Butao Zhang Replied Message | From | tcgaoxiong | | Date | 1/15/2024 18:27 | | To | dev@hive.apache.org | | Subject | review help | Hi, Can anyone review this pr help? HIVE-27960.

review help

Hi, Can anyone review this pr help? HIVE-27960. The test has passed. Thanks. gaoxiong

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

On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 2.3 branch is being actively maintained so far). Hopefully this will be the last release in the branch-2 line. +1 on making Hive 1 EOL for the time being. Chao On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan wrote: > > +1 for

RE: [EXTERNAL] Re: [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x

+1, It is needed only for upgrading from Hive 1.x/2.x to 3.x and not relevant for 4.x. We can retain it in 3.x release line only. -Sankar -Original Message- From: Attila Turoczy Sent: Wednesday, January 10, 2024 7:04 PM To: dev@hive.apache.org Subject: [EXTERNAL] Re: [DISCUSS]

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

+1 for making both Hive 1&2 EOL -Sankar -Original Message- From: Attila Turoczy Sent: Wednesday, January 10, 2024 7:37 PM To: dev@hive.apache.org Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x [You don't often get email from aturo...@cloudera.com.invalid. Learn

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

+1 for making it EOL for Hive 1 and Hive 2. I do not think these 2 product branches are relevant in 2023. -Attila On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko wrote: > +1 for marking Hive 1.x EOL > > Assuming no volunteers willing to take ownership of branch-2 maintenance, > +1 to declare

Re: [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x

Big +1 from me. As we shift our focus from ACID to Iceberg I do not think it is relevant anymore. Also as Butao highlighted it has a CVE as well. Let's remove it, and if eventually something is needed (highly doubt) then we can revisit the decision at that time. Due to the extensive history of

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

+1 for marking Hive 1.x EOL Assuming no volunteers willing to take ownership of branch-2 maintenance, +1 to declare it EOL as well. Regards, Denys

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

+1 for marking Hive 1.x EOL. I will also take the opportunity to ask again for Hive 2.x. Are there people willing to take on the maintenance of the branch-2 line? The people who take on the maintenance of the release line should (as a bare minimum) ensure that all CVEs (existing and new ones) are

Re: How to use `engine` introduced by HIVE-22046

Hi Butao, Thanks for reminding us about the issue. +1 for the approach. Thanks, Okumin On Mon, Jan 8, 2024 at 1:38 PM Butao Zhang wrote: > > Hi, dev > Bump this thread! > I just filed a ticket to track this incompatibility issues about hms > column stats thrift api. I think we can fix this

Re: [DISCUSS] Deprecate/Drop upgrade-acid module from 4.x

+1. I am not sure the use case of upgrade-acid module, but it seems that this module is rarely used in my world. I think maybe the first safe step is deprecating this module to let users know that this module should not be used any more. BTW, my idea tells me that this module used the old

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

I will start a vote to mark Hive 1.x EOL next week. Let me know if anyone has concerns around it. The main reason to mark a release line EOL is: if we have a CVE & if we don't release all the active lines with the fix we can't announce that & the PMC would be flagged every quarter for delaying

[DISCUSS] Deprecate/Drop upgrade-acid module from 4.x

Hi Folks, Wanted to know thoughts on removing the upgrade-acid module[1] from 4.x. The javadoc on one of the main files[2] read "This utility is designed to help with upgrading Hive 2.x to Hive 3.0". I think this is a 2.x to 3.x thing and doesn't look relevant for Hive-4.x. Checking the git log, I

Re: 4.0 documentation - Confluence limitations?

When we discussed last time, all of us were in favour and wanted to have documentation as part of our website per version, but we realised that isn't very much chasable considering the number of volunteers we have, so we decided to go with improving the existing wiki pages & add new additions to

Re: Force coding style in hive precommit

+1 I think most of the devs use IntelliJ, where no other plugin needed to have a Code Style. It can even import Eclipse formatting file. Regards, RZ On Mon, Jan 8, 2024 at 10:22 AM Stamatis Zampetakis wrote: > +1 for enforcing style on new code. It will definitely save us from > additional

Re: 4.0 documentation - Confluence limitations?

Hi Zsolt, The current hive website is built with hugo, so +1 from me :) We do have a few doc pages written in hugo, example : https://hive.apache.org/developement/quickstart/ To add a new page we will need to add a new markdown file in the correct location in the hive-site repo and hugo will

Re: 4.0 documentation - Confluence limitations?

Hey Zsolt, There have been a few discussions in the past about moving the documentation from the wiki to the website and from what I recall people were more or less in favor of moving towards this direction. The main thing missing is volunteers that are willing to take on this migration step.

Re: Force coding style in hive precommit

+1 for enforcing style on new code. It will definitely save us from additional review cycles. Although I like checkstyle I tend to prefer tools that can automatically apply and fix style violations such as spotless [1]. It seems that the spotless plugin can be configured to enforce formatting

Re: Force coding style in hive precommit

I think giving a warning is something that nobody will check. It could only make sense if it is formatted in a way that it cannot be overseen. In every other case, it is just ignored. And also, we are already full of warnings so I'm afraid it can just hide in the noise. Sorry, I don't know how it

Re: Force coding style in hive precommit

+1, to have a checkstyle build. I am strongly against doing that big refactor to make just checkstyle happy, such a refactor will make backports to Hive lower branches tough and the life of folks maintaining downstream forks quite painful. We should enforce same kind of stuff like in Tez/Hadoop,

Re: Force coding style in hive precommit

thanks for the responses so far! I'm a bit against the one-time huge refactor commit as we don't need that (but I can be convinced of course), because checkstyle can be set up to warn only on style issues in the new/touched bits in the PR (or at least that's how it works in tez), that's what we

Re: Force coding style in hive precommit

+1 BTW, We have a independent checkstyle file under iceberg module https://github.com/apache/hive/tree/master/iceberg/checkstyle . I think we need to consider unifing the checkstyle in all the sub-module. Thanks, Butao Zhang Replied Message | From | Zsolt Miskolczi | | Date |

Re: Force coding style in hive precommit

+1 In case there is an agreement about the coding style, we can prepare a tool that enforces that style at compile time. Run a tool one time to re-format all the existing code once. And turn on a compile time check. Iceberg did the same approach, they had one huge commit with almost 4k files

4.0 documentation - Confluence limitations?

In confluence, page names should be unique in a given space. As I see, Apache Hive has its own space. And now comes the tricky part: with 4.0 documentation, we didn't create a new space, just a 4.0 parent page. We create a copy of existing pages under the umbrella of this page:

Re: Force coding style in hive precommit

+1 As it would improve maintainability and code reviews. Sometimes small indentation/styling issues would kill review cycle time and we can easily avoid it before requesting review. Enforcing more rules around it definitely boost guaranteeing quality. We can integrate it with git hooks. If we

Re: Force coding style in hive precommit

+1, We do have a documentation round it as well: https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToContribute-CodingConventions so it makes sense to enforce it as well. Right now we have a small section around this in documentation, We can also expand this to a new page and

Re: How to use `engine` introduced by HIVE-22046

Hi, dev Bump this thread! I just filed a ticket to track this incompatibility issues about hms column stats thrift api. I think we can fix this at its root in HMS side and then any other third components will not suffer from this issue. https://issues.apache.org/jira/browse/HIVE-27984

Force coding style in hive precommit

Hi All! What do you think about forcing coding style in Hive precommit? I remember, back in the old days, precommit printed some warnings in case some coding style (formatting, indentation, naming convention, etc.) problems were found in the patch, now it's simply not used, I guess since we're

Meet our keynote speakers and register to Community Over Code EU!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] * Merge with the ASF EUniverse!The registration for

Re: Help with Docker Apache/Hive metastore using mysql remote database

There is no mysql driver file in following repo https://repo1.maven.org/maven2/org On Mon, Dec 18, 2023 at 3:10 AM Simhadri G wrote: > > We can modify the Dockerfile to wget the necessary driver and copy it to > /opt/hive/lib/ . This should make it work. The diff is attached below: > > > diff

Re: Help with Docker Apache/Hive metastore using mysql remote database

Hi, You can download it from here: https://repo1.maven.org/maven2/mysql/mysql-connector-java/8.0.29/mysql-connector-java-8.0.29.jar Regards, Akshat On Thu, Dec 21, 2023 at 1:40 AM Sanjay Gupta wrote: > There is no mysql driver file in following repo > https://repo1.maven.org/maven2/org > > On

Re:Re: ci execute too long, 13h..., branch2

get, thanks for you reply. At 2023-12-19 12:26:46, "Akshat m" wrote: >Hi, > >We do have a timeout mechanism in place, for branch-2 it is set to 24hrs: >https://github.com/apache/hive/blob/659aa5d94ffc15696c4729694ba68a77a58c2074/Jenkinsfile#L70 > >I couldn't find any recent PRs

Re: ci execute too long, 13h..., branch2

Hi, We do have a timeout mechanism in place, for branch-2 it is set to 24hrs: https://github.com/apache/hive/blob/659aa5d94ffc15696c4729694ba68a77a58c2074/Jenkinsfile#L70 I couldn't find any recent PRs with test passed label for branch-2 to compare an appropriate time for this job completion,

ci execute too long, 13h..., branch2

hi, http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-4955/1/pipeline/623/ split-16 is running more than 13h, but no test fail on this split. Is it have timeout mechanism or other mechanism to stop it.

Re: Help with Docker Apache/Hive metastore using mysql remote database

We can modify the Dockerfile to wget the necessary driver and copy it to /opt/hive/lib/ . This should make it work. The diff is attached below: diff --git a/packaging/src/docker/Dockerfile b/packaging/src/docker/Dockerfile --- a/packaging/src/docker/Dockerfile (revision

<    1   2   3   4   5   6   7   8   9   10   >