Re: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Alessandro Solimando]

Great news, Simhadri, very well deserved!

On Thu, 18 Apr 2024 at 15:07, Simhadri G  wrote:

> Thanks everyone!
> I really appreciate it, it means a lot to me :)
> The Apache Hive project and its community have truly inspired me . I'm
> grateful for the chance to contribute to such a remarkable project.
>
> Thanks!
> Simhadri Govindappa
>
> On Thu, Apr 18, 2024 at 6:18 PM Sankar Hariappan
>  wrote:
>
>> Congrats Simhadri!
>>
>>
>>
>> -Sankar
>>
>>
>>
>> *From:* Butao Zhang 
>> *Sent:* Thursday, April 18, 2024 5:39 PM
>> *To:* user@hive.apache.org; dev 
>> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New Committer: Simhadri Govindappa
>>
>>
>>
>> You don't often get email from butaozha...@163.com. Learn why this is
>> important 
>>
>> Congratulations Simhadri !!!
>>
>>
>>
>> Thanks.
>>
>>
>> --
>>
>> *发件人**:* user-return-28075-butaozhang1=163@hive.apache.org <
>> user-return-28075-butaozhang1=163@hive.apache.org> 代表 Ayush Saxena <
>> ayush...@gmail.com>
>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>> *收件人**:* dev ; user@hive.apache.org <
>> user@hive.apache.org>
>> *主题**:* [ANNOUNCE] New Committer: Simhadri Govindappa
>>
>>
>>
>> Hi All,
>>
>> Apache Hive's Project Management Committee (PMC) has invited Simhadri
>> Govindappa to become a committer, and we are pleased to announce that he
>> has accepted.
>>
>>
>>
>> Please join me in congratulating him, Congratulations Simhadri, Welcome
>> aboard!!!
>>
>>
>>
>> -Ayush Saxena
>>
>> (On behalf of Apache Hive PMC)
>>
>

Re: Kill the Pig 

[Alessandro Solimando]

+1 from me, let's just make sure we make a good salame out of it :)

Best regards,
Alessandro

On Thu, 20 Apr 2023 at 10:50, Attila Turoczy  wrote:

> Hi All,
>
> In Hive we have a pretty old component from 1972 and this is the Pig. Pig
> was cool somewhere in 2008, but nowadays it does not have any value in the
> big data world. Even the last small release of big was 6 years ago in 2017,
> also the pig community has pretty much died. Because this component is
> obsolete I would suggest removing it from Hive 4.0. The hive 3 will still
> contain it, but I think this is a right time to remove those components
> that are not valuable for the community.
>
> What do you think about it?
>
> Ps: If nobody wrote it back, It would mean I could kill the pig (rof rof)
> :)
>
> -Attila
>

Re: [ANNOUNCE] New committer for Apache Hive: Alessandro Solimando

[Alessandro Solimando]

Thanks everyone for your kind messages, I am truly honored to be part of
this community and I am extremely happy to have the chance to work with you
all.

Best regards,
Alessandro

On Thu, 9 Feb 2023 at 08:17, Krisztian Kasa 
wrote:

> Congratulations Alessandro!
>
> On Thu, Feb 9, 2023 at 7:51 AM Akshat m  wrote:
>
> > Congratulations Alessandro :)
> >
> > Regards,
> > Akshat Mathur
> >
> > On Thu, Feb 9, 2023 at 12:11 PM Mahesh Raju Somalaraju <
> > maheshra...@cloudera.com> wrote:
> >
> > > Congratulations Alessandro !!
> > >
> > > -Mahesh Raju S
> > >
> > > On Thu, Feb 9, 2023 at 1:31 AM Naveen Gangam 
> > wrote:
> > >
> > >> The Project Management Committee (PMC) for Apache Hive has invited
> > >> Alessandro Solimando (asolimando) to become a committer and is pleased
> > >> to announce that he has accepted.
> > >>
> > >> Contributions from Alessandro:
> > >> He has authored 30 patches for Hive, 18 for Apache Calcite and has
> > >> done many code reviews for other contributors. Vast experience and
> > >> knowledge in SQL Compiler and Optimization. His most recent work was
> > >> added support for histogram-based column stats in Hive.
> > >>
> > >> https://issues.apache.org/jira/issues/?filter=12352498
> > >>
> > >> Being a committer enables easier contribution to the project since
> > >> there is no need to go via the patch submission process. This should
> > >> enable better productivity.A PMC member helps manage and guide the
> > >> direction of the project.
> > >>
> > >> Congratulations
> > >> Hive PMC
> > >>
> > >
> >
>

Re: [ANNOUNCE] New committer for Apache Hive: Laszlo Vegh

[Alessandro Solimando]

Congrats, Laszlo!

Best regards,
Alessandro

On Tue, 7 Feb 2023 at 13:24, Naveen Gangam  wrote:

> The Project Management Committee (PMC) for Apache Hive has invited Laszlo
> Vegh (veghlaci05) to become a committer and we are pleased
> to announce that he has accepted.
>
> Contributions from Laszlo:
>
> He has authored 25 patches. Significant contributions to stabilization of
> ACID compaction. Helped review other patches as well.
>
>
> https://github.com/apache/hive/pulls?q=is%3Amerged+is%3Apr+author%3Aveghlaci05
>
> Being a committer enables easier contribution to the project since there
> is no need to go via the patch submission process. This should enable
> better productivity.A PMC member helps manage and guide the direction of
> the project.
>
> Congratulations
> Hive PMC
>

Re: unsubscribe

[Alessandro Solimando]

Hello, in order to unsubscribe from the list you need to send an email
here: user-unsubscr...@hive.apache.org

On Thu 2 Feb 2023, 16:47 Gobinda Paul,  wrote:

> unsubscribe
> --
> *From:* zhangxin011...@126.com 
> *Sent:* Thursday, February 2, 2023 9:50 AM
> *To:* user@hive.apache.org 
> *Subject:* unsubscribe
>
>
> unsubscribe
>

Re: unsubscribe

[Alessandro Solimando]

Hello, in order to unsubscribe from the list you need to send an email
here: user-unsubscr...@hive.apache.org

On Thu 2 Feb 2023, 04:51 ,  wrote:

> unsubscribe
>

Re: [ANNOUNCE] New PMC Member: Krisztian Kasa

[Alessandro Solimando]

Congratulations Krisztian, very well deserved! :)

On Mon, 30 Jan 2023 at 17:34, László Bodor 
wrote:

> Yay! Very well deserved. Krisztian has a broad knowledge of Hive and an
> extremely deep level of experience with the compiler itself (which is a
> huge beast we all know), looking forward to seeing further contributions!
>
> Naveen Gangam  ezt írta (időpont: 2023.
> jan. 30., H, 17:23):
>
>> Hello Hive Community,
>> Apache Hive PMC is pleased to announce that Krisztian Kasa (username:
>> krisztiankasa) has accepted the Apache Hive PMC's invitation to become PMC
>> Member, and is now our newest PMC member. Please join me in congratulating
>> Krisztian !!!
>>
>> He has been an active member in the hive community across many aspects of
>> the project. Many thanks to Krisztian for all the contributions he has
>> made
>> and looking forward to many more future contributions in the expanded
>> role.
>>
>> https://github.com/apache/hive/commits?author=kasakrisz
>>
>> * 162 commits in master
>> * 124 reviews in master
>> * Reported 159 JIRAS
>>
>> Cheers,
>> Naveen (on behalf of Hive PMC)
>>
>

Re: [ANNOUNCE] New PMC Member: Laszlo Bodor

[Alessandro Solimando]

Congratulations Laszlo, very well deserved, thanks for all your hard work.

Best regards,
Alessandro

On Fri, 27 Jan 2023 at 22:33, Naveen Gangam 
wrote:

> Hello Hive Community,
> Apache Hive PMC is pleased to announce that Laszlo Bodor
> (username:abstractdog) has accepted the Apache Hive PMC's invitation to
> become PMC Member, and is now our newest PMC member. Please join me in
> congratulating Laszlo !!!
>
> He has been an active member in the hive community across many aspects of
> the project. Many thanks to Laszlo for all the contributions he has made
> and looking forward to many more future contributions in the expanded role.
>
> https://github.com/apache/hive/commits?author=abstractdog
>
> * 96 commits in master [2]
> * 66 reviews in master [3]
> * Reported 163 JIRAS [6]
>
> Cheers,
> Naveen (on behalf of Hive PMC)
>

Re: [EXTERNAL] [ANNOUNCE] New PMC Member: Stamatis Zampetakis

[Alessandro Solimando]

Congratulations Stamatis,
very well deserved!

Best regards,
Alessandro

On Fri 13 Jan 2023, 19:57 Chris Nauroth,  wrote:

> Congratulations, Stamatis!
>
> Chris Nauroth
>
>
> On Fri, Jan 13, 2023 at 10:46 AM Simhadri G  wrote:
>
> > Congratulations Stamatis!
> >
> > On Sat, 14 Jan 2023, 00:12 Sankar Hariappan via user, <
> > user@hive.apache.org>
> > wrote:
> >
> > > Congrats Stamatis! Well deserved one 
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Sankar
> > >
> > >
> > >
> > > *From:* Naveen Gangam 
> > > *Sent:* Saturday, January 14, 2023 12:03 AM
> > > *To:* dev ; user@hive.apache.org
> > > *Cc:* zabe...@apache.org
> > > *Subject:* [EXTERNAL] [ANNOUNCE] New PMC Member: Stamatis Zampetakis
> > >
> > >
> > >
> > > Hello Hive Community,
> > >
> > > Apache Hive PMC is pleased to announce that Stamatis Zampetakis has
> > > accepted the Apache Hive PMC's invitation to become PMC Member, and is
> > now
> > > our newest PMC member. Please join me in congratulating Stamatis !!!
> > >
> > >
> > >
> > > He has been an active member in the hive community across many aspects
> of
> > > the project. Many thanks to Stamatis for all the contributions he has
> > made
> > > and looking forward to many more future contributions in the expanded
> > role.
> > >
> > >
> > >
> > > Cheers,
> > >
> > > Naveen (on behalf of Hive PMC)
> > >
> >
>

Re: [EXTERNAL] Re: [ANNOUNCE] New PMC Member: Ayush Saxena

[Alessandro Solimando]

Congratulations and very well deserved Ayush!

@hernan: this is not how things work in Apache projects, committership and
PMC membership are based on merit, not affiliation or anything else. It
suffices to look at all the hard work that Ayush has put in over time (both
contributions but also reviews, release testing/voting, presence in the
ML), it's clear that this is based on merit and therefore congratulations
are in order.

On Tue, 20 Dec 2022 at 09:57, hernan saab via user 
wrote:

> I don’t understand the congrats. I always thought only developers directed
> by managers would apply for a role like this.
> What am I missing here?
>
>
> Sent from Yahoo Mail for iPad 
>
> On Monday, December 19, 2022, 11:49 PM, Stamatis Zampetakis <
> zabe...@gmail.com> wrote:
>
> Congrats Ayush! Very well deserved!
>
> Thanks for all the hard work that you are putting for the project and
> always being there when people ask for help.
>
> Best,
> Stamatis
>
> On Tue, Dec 20, 2022 at 7:51 AM Sankar Hariappan via user <
> user@hive.apache.org> wrote:
>
> Congrats Ayush!
>
>
>
> Thanks,
>
> Sankar
>
>
>
> *From:* Simhadri G 
> *Sent:* Tuesday, December 20, 2022 12:16 PM
> *To:* user@hive.apache.org
> *Cc:* dev ; ayushsax...@apache.org
> *Subject:* [EXTERNAL] Re: [ANNOUNCE] New PMC Member: Ayush Saxena
>
>
>
> Congratulations Ayush
>
>
>
> On Tue, 20 Dec 2022, 06:42 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: Proposal: Revamp Apache Hive website.

[Alessandro Solimando]

Hi everyone,
thanks Simhadri for pushing this forward.

I like the look and feel of the new website, and I agree with Stamatis that
having the website sources in the Hive repo, and automatically publishing
the site upon commits would be very beneficial.

Best regards,
Alessandro

On Thu, 15 Sept 2022 at 23:11, Stamatis Zampetakis 
wrote:

> Hi all,
>
> It's great to see some effort in improving the website. The POC from
> Simhadri looks really cool; I didn't check the content but I love the look
> and feel.
>
> Now regarding the current process for modifying and updating the website
> there is some info in this relatively recent thread [1].
>
> Moving forward, I would really like to have the source code of the website
> (markdown etc) in the main repo of the project [2], and use GitHub actions
> to automatically build and push the content to the site repo [3] per commit
> basis.
> This workflow is used in Apache Calcite and I find it extremely convenient.
>
> Best,
> Stamatis
>
> [1] https://lists.apache.org/thread/4b6x4d6z4tgnv4mo0ycg30y4dlt0msbd
> [2] https://github.com/apache/hive
> [3] https://github.com/apache/hive-site
>
> On Thu, Sep 15, 2022 at 10:50 PM Ayush Saxena  wrote:
>
>> Owen,
>> I am not sure if I am catching you right, But now the repository for the
>> website has changed, we no longer use our main *hive.git* repository for
>> the website, We are using the* hive-site *repository for the website,
>> The migration happened this year January I suppose.
>>
>> Can give a check to the set of commit here from: gmcdonald
>>  and
>> Humbedooh 
>> https://github.com/apache/hive-site/commits/main
>>
>> Now whatever you push to main branch of hive-site(
>> https://github.com/apache/hive-site) it gets published on the *asf-site*
>> branch by the buildbot(
>> https://github.com/apache/hive-site/commits/asf-site)
>>
>> Simhadri's changes will be directed to the main branch of the hive-site
>> repo and they will get auto published on the asf-site branch, I tried this
>> a couple of months back and it indeed worked that way. Let me know if we
>> are missing anything on this, I tried to find threads around this but not
>> sure if it is in private@ or so, couldn't find, I will try again and if
>> there is something around that what needs to be done, I will have a word
>> with the Infra folks and get that sorted, if it isn't already.
>>
>> -Ayush
>>
>> On Fri, 16 Sept 2022 at 01:49, Owen O'Malley 
>> wrote:
>>
>>> Look at the threads and talk to Apache Infra. They couldn't make it work
>>> before. We would have needed to manually publish to the asf-site branch.
>>>
>>> On Thu, Sep 15, 2022 at 7:54 PM Simhadri G 
>>> wrote:
>>>
 Thanks Ayush, Pau Tallada and Owen O'Malley for the feedback!

 @Owen , This website revamp indeed replaces the website with markdown
 as you have mentioned. I have referred to your PR for some of the content
 for the site.
 The actual code for the website is here:
 https://github.com/simhadri-g/hive-site/tree/new-site

 Once we add markdown files to the source code under /content/ , hugo
 will rebuild the files and generate the static html files in ./public/
 directory.
 I have copied over these static files to a separate repo and
 temporarily hosted it with gh-pages to start the mail chain.

  For the final site, I am already trying to automate this with github
 actions. So, as soon as any new changes are made to the site branch, the
 github actions will automatically tigger and update the site.

 Thanks!

 On Fri, Sep 16, 2022 at 12:17 AM Owen O'Malley 
 wrote:

> I found it - https://github.com/apache/hive/pull/1410
>
> On Thu, Sep 15, 2022 at 6:42 PM Owen O'Malley 
> wrote:
>
>> I had a PR to replace the website with markdown. Apache Infra was
>> supposed to make it autopublish. *sigh*
>>
>> .. Owen
>>
>> On Thu, Sep 15, 2022 at 4:23 PM Pau Tallada  wrote:
>>
>>> Hi,
>>>
>>> Great work!
>>> +1 on updating it as well
>>>
>>> Missatge de Ayush Saxena  del dia dj., 15 de
>>> set. 2022 a les 17:40:
>>>
 Hi Simhadri,
 Thanx for the initiative, +1 on updating our current website.
 The new website looks way better than the existing one.
 Can create a Jira and link this to that after a couple of days if
 there aren’t any objections to the move, so as people can drop further
 suggestions over there.

 -Ayush

 > On 15-Sep-2022, at 8:33 PM, SG  wrote:
 >
 > Hi Everyone,
 >
 > The existing apache hive website https://hive.apache.org/ hasn't
 been
 > updated for a very long time. Additionally, I was not able to
 build the
 > docker image associated with the 

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

[Alessandro Solimando]

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://lists.apache.org/thread/n245dd23kb2v3qrrfp280w3pto89khxj
>
>

Re: Does Hive support Dry run mode

[Alessandro Solimando]

Hi Sohail,
no progress AFAICT, but using EXPLAIN as a workaround sounds good to me, I
don't see any negative side-effects of that.

Best regards,
Alessandro

On Wed, 6 Apr 2022 at 06:52, Sohail Khan  wrote:

> Hello team,
>
> I came across
> https://issues.apache.org/jira/browse/HIVE-2478
>
>
> Is this JIRA implemented or is still in development . If it’s still in
> development do we have workaround, I read in the comments for using EXPLAIN
> to validate queries. Is that the recommended practice?
>
> Thanks and Regards
> Sohail khan
> --
> Thanks and Regards
> Sohail Khan
> Dept. Computer and Information Sciences
>

Re: write access to the wiki

[Alessandro Solimando]

Thanks Peter, it's working fine!

On Thu, 3 Mar 2022 at 14:56, Peter Vary  wrote:

> Hi Alessandro,
>
> I have added you to the wiki.
> Could you please check it?
>
> Thanks,
> Peter
>
> > On 2022. Mar 3., at 13:29, Alessandro Solimando <
> alessandro.solima...@gmail.com> wrote:
> >
> > Hello,
> > I have recently gone through regenerating some thrift files, and I have
> noticed that the info in the wiki is outdated, I'd like to contribute an
> updated version.
> >
> > Can I get write access from a wiki admin?
> > My confluence id is "asolimando".
> >
> > PS: talking to some Hive committers and PMCs, we were wondering if all
> PMCs could be added to the admin role, what do you think?
> >
> > Thanks,
> > Alessandro
>
>

write access to the wiki

[Alessandro Solimando]

Hello,
I have recently gone through regenerating some thrift files, and I have
noticed that the info in the wiki is outdated, I'd like to contribute an
updated version.

Can I get write access from a wiki admin?
My confluence id is "asolimando".

PS: talking to some Hive committers and PMCs, we were wondering if all PMCs
could be added to the admin role, what do you think?

Thanks,
Alessandro

Re: help with beeline connection to hive

[Alessandro Solimando]

Hi Bitfox,
did you check if HS2 is indeed running on port 1? ("sudo lsof -i -P -n
| grep LISTEN" for instance).

IIRC the default credentials are "hive/hive", can you try that too?

HTH,
Alessandro

On Wed, 23 Feb 2022 at 03:17, Bitfox  wrote:

> Hello
>
> I have hive 2.3.9 installed by default on localhost for testing.
> HDFS is also installed on localhost, which works correctly b/c I have
> already used the file storage feature.
>
> I didn't change any configure files for hive.
>
> I can login into hive shell:
>
> hive> show databases;
>
> OK
>
> default
>
> Time taken: 4.458 seconds, Fetched: 1 row(s)
>
>
>
> After started hiveserver2 which works online, I can't connect via beeline:
>
>
> beeline> !connect jdbc:hive2://localhost:1/default
>
> Connecting to jdbc:hive2://localhost:1/default
>
> Enter username for jdbc:hive2://localhost:1/default: APP
>
> Enter password for jdbc:hive2://localhost:1/default: 
>
> 22/02/23 10:11:41 [main]: WARN jdbc.HiveConnection: Failed to connect to
> localhost:1
>
> Could not open connection to the HS2 server. Please check the server URI
> and if the URI is correct, then ask the administrator to check the server
> status.
>
> Error: Could not open client transport with JDBC Uri:
> jdbc:hive2://localhost:1/default: java.net.ConnectException: Connection
> refused (Connection refused) (state=08S01,code=0)
>
>
>
> It prompts me to input username and password.
>
> I have tried both empty user/pass, and user "APP"/pass "mine".
>
> Neither of them will work.
>
>
>
> How can I fix this and connect to Hive correctly via beeline?
>
>
> Sorry I am the newbie to Hive.
>
>
> Thanks a lot.
>

Re: Unable to connect to keberized hive using beeline

[Alessandro Solimando]

Hi Akshay,
the Hive ML is for the OSS version of Hive, for the vendor's packaged
versions it's probably better to reach out to the vendor and/or check their
documentation/knowledge base.

This is because the Apache source code might differ from what is packaged
by the vendor, and it's hard to help out in such cases.

Best regards,
Alessandro

On Tue, 1 Feb 2022 at 07:57, Akshay Wani  wrote:

> Hello,
>
> I'm trying to connect to keberized hive (CDH and HDP) from my local
> machine with standalone setup of Apache hive, but it is giving kerberos
> error : 'ERROR transport.TSaslTransport: SASL negotiation failure
> javax.security.sasl.SaslException: GSS initiate failed'.
>
> Kerberos client setup is done successfully and I'm able to do kinit also
> using my machine but when I'm trying to connect to hive it is giving the
> error.
>
> Can you please help me in this regard?
>
> Thanks,
> Akshay
>

Re: [DISCUSS] Properties for scheduling compactions on specific queues

[Alessandro Solimando]

Hi Stamatis,
the proposal seems reasonable to me.

I think that setting the two properties you mention, independently from the
underlying execution engine in use, should lead to the same result.

In addition, I also agree that we should deprecate the per-execution engine
properties.

Best regards,
Alessandro

On Mon, 31 Jan 2022 at 10:51, Stamatis Zampetakis  wrote:

> Hi all,
>
> This email is an attempt to converge on which Hive/Tez/MR properties
> someone should use in order to schedule a compaction on specific queues.
> For those who are not familiar with how queues are used the YARN capacity
> scheduler documentation [1] gives the general idea.
>
> Using specific queues for compaction jobs is necessary to be able to
> efficiently allocate resources for maintenance tasks (compaction) and
> production workloads. Hive provides various ways to control the queues used
> by the compactor and there have been various tickets with improvements and
> fixes in this area (see list below).
>
> The granularity we can select queues for compactions (all tables vs. per
> table) currently depends on which compactor is in use (MR vs Query based)
> and boils down to the following properties:
>
> Global configuration:
> * hive.compactor.job.queue
> * mapred.job.queue.name
> * tez.queue.name
>
> Per table/statement configuration (table properties):
> * compactor.mapred.job.queue.name (before HIVE-20723)
> * compactor.hive.compactor.job.queue (after HIVE-20723)
>
> Things are a bit blurred with respect to what properties someone should
> use to achieve the desired result. Some changes, such as HIVE-20723, raise
> backward compatibility concerns and other changes seem to have a larger
> impact than the one specifically designed for. For example, after
> HIVE-25595, map reduce queue properties can have an impact on the compactor
> queues even when Tez is in use.
>
> In order to avoid confusion and ensure long term support of these queue
> selection features we should clarify which of the above properties should
> be used.
>
> Given the current situation, I would propose to officially support only
> the following:
> * hive.compactor.job.queue
> * compactor.hive.compactor.job.queue
> and align the implementation based on these (if necessary). In other
> words, Hive users should not use mapred.job.queue.name and tez.queue.name
> explicitly at least when it comes to the compactor. Hive should set them
> transparently (as it happens now in various places) based on
> [compactor.]hive.compactor.job.queue.
>
> What do people think? Are there other ideas?
>
> Best,
> Stamatis
>
> [1]
> https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html
>
> HIVE-11997: Add ability to send Compaction Jobs to specific queue
> HIVE-13354: Add ability to specify Compaction options per table and per
> request
> HIVE-20723: Allow per table specification of compaction yarn queue
> HIVE-24781: Allow to use custom queue for query based compaction
> HIVE-25801: Custom queue settings is not honoured by Query based
> compaction StatsUpdater
> HIVE-25595: Custom queue settings is not honoured by compaction
> StatsUpdater
>

Re: How can I know use execute or executeQuery

[Alessandro Solimando]

Hi Igyu,
sending different SQL statements is exactly what beeline has to handle, I'd
have a look at how they handle this:
https://github.com/apache/hive/tree/master/beeline (this

seems a good starting point).

HTH,
Alessandro

On Wed, 15 Sept 2021 at 03:50, igyu  wrote:

> SQL is writed by user.
> user can write "show tables", "use db"or "select * from table".
> so I don't know SQL before send to server.
> when SQL into the server how can I know use execute or executeQuery.
>
> SQL type is too many
>
> --
> igyu
>