Re: [ANNOUNCE] New Committer: Stephen Carlin

2024-07-18 Thread Denys Kuzmenko
Congrats Stephen!

On Thu, Jul 18, 2024 at 7:01 AM Akshat m  wrote:

> Congratulations Stephen !
>
> Regards
> Akshat
>
> On Thu, Jul 18, 2024 at 8:07 AM kokila narayanan <
> kokilanarayana...@gmail.com> wrote:
>
>> Congratulations Stephen !!
>>
>> Regards,
>> Kokila N
>>
>> On Thu, 18 Jul, 2024, 07:57 Naresh P R,  wrote:
>>
>>> Congratulations Stephen !!!
>>> —-
>>> Regards,
>>> Naresh P R
>>>
>>> On Wed, Jul 17, 2024 at 5:21 AM Stamatis Zampetakis 
>>> wrote:
>>>
 Hi All,

 Apache Hive's Project Management Committee (PMC) has invited Stephen
 Carlin to become a committer, and we are pleased to announce that he
 has accepted.

 Steve has been contributing to the project since 2019. He has improved
 many aspects of the project notably the query compiler and the
 cost-based optimizer enhancing performance and fixing multiple bugs.

 Stephen, welcome, thank you for your contributions, and we look forward
 to your further interactions with the community!

 Please review the guidelines for new committers [1] and take
 additional actions as needed.

 Stamatis Zampetakis (on behalf of the Apache Calcite PMC)

 [1] https://cwiki.apache.org/confluence/display/Hive/HowToCommit

>>>


Re: Fw: apache/hive security vulnerabilities.

2024-06-21 Thread Denys Kuzmenko
jackson-databind:2.9.4 comes from Calcite avatica:1.12.0 shaded jar:
https://mvnrepository.com/artifact/org.apache.calcite.avatica/avatica/1.12.0

that jar has also reported vulnerability :CVE-2022-36364, we should try to 
upgrade it.

Another one is htrace-core:3.1.0-incubating from accumulo-core:1.10.1
https://mvnrepository.com/artifact/org.apache.htrace/htrace-core/3.1.0-incubating

Same story: CVE-2022-36364



Re: apache/hive security vulnerabilities.

2024-06-19 Thread Denys Kuzmenko
Hi Sreek,

Oh, thanks! Ideally docker image should be build from Hive-4.0 branch artifacts 
via the GH action. Let me check, I just hope it wasn't manually uploaded


Re: apache/hive security vulnerabilities.

2024-06-19 Thread Denys Kuzmenko
Hi,

Hive-4.0 use jackson-databind version 2.16.1. I don't see any CVEs reported in 
maven central for that artifact:
https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind/2.16.1


com.fasterxml.jackson
jackson-bom
2.16.1
pom
import




Re: Fwd: about hive4.0.0 error

2024-06-19 Thread Denys Kuzmenko
Are you using MR execution mode? it was deprecated, see warning
"Hive-on-MR is deprecated in Hive 2 and may not be available in the future 
versions. Consider using a different execution engine"

On 2024/06/19 04:59:22 张三 wrote:
> -- Forwarded message -
> 发件人: 张三 
> Date: 2024年6月19日周三 12:55
> Subject: about hive4.0.0 error
> To: 
> 
> 
> Dear Hive team,
> 
> I encountered an issue while using the latest version of Hive, 4.0.0. I am
> not sure if this is a bug. The details are as follows: I am using Hadoop
> version 3.3.6 and have set up a fully distributed cluster. The Hive version
> is 4.0.0, with one master server and one client. Currently, I am connecting
> to Hive via the Beeline client. When executing a join in Hive, I
> encountered the following error:
> 
> ```
> 
> 0: jdbc:hive2://node1:1> SELECT emp.emp_id, emp.emp_name, dept.dept_name
> . . . . . . . . . . . . . .> FROM emp
> . . . . . . . . . . . . . .> JOIN dept ON  emp.dept_id = dept.dept_id;
> INFO  : Compiling
> command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc):
> SELECT emp.emp_id, emp.emp_name, dept.dept_name
> FROM emp
> JOIN dept ON  emp.dept_id = dept.dept_id
> INFO  : No Stats for default@emp, Columns: emp_name, dept_id, emp_id
> INFO  : No Stats for default@dept, Columns: dept_name, dept_id
> INFO  : Semantic Analysis Completed (retrial = false)
> INFO  : Created Hive schema:
> Schema(fieldSchemas:[FieldSchema(name:emp.emp_id, type:int, comment:null),
> FieldSchema(name:emp.emp_name, type:strin
> g, comment:null), FieldSchema(name:dept.dept_name, type:string,
> comment:null)], properties:null)INFO  : Completed compiling
> command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc);
> Time taken: 0.894 seconds
> INFO  : Concurrency mode is disabled, not creating a lock manager
> INFO  : Executing
> command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc):
> SELECT emp.emp_id, emp.emp_name, dept.dept_name
> FROM emp
> JOIN dept ON  emp.dept_id = dept.dept_id
> WARN  : Hive-on-MR is deprecated in Hive 2 and may not be available in the
> future versions. Consider using a different execution engine (i.e. tez
> ) or using Hive 1.X releases.INFO  : Query ID =
> root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc
> INFO  : Total jobs = 1
> INFO  : Starting task [Stage-4:MAPREDLOCAL] in serial mode
> ERROR : Execution failed with exit status: 1
> ERROR : Obtaining error information
> ERROR :
> Task failed!
> Task ID:
>   Stage-4
> 
> Logs:
> 
> ERROR : /tmp/root/hive.log
> ERROR : FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask
> INFO  : Completed executing
> command(queryId=root_20240619122107_48e50dbd-9e12-4743-9652-f266165811bc);
> Time taken: 4.461 seconds
> Error: Error while compiling statement: FAILED: Execution Error, return
> code 1 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask (state=08S0
> 1,code=1)
> 
> ```
> 
>   I checked the log on the Hive server at /tmp/root/hive.log and found the
> following error information:
> 
> ```
> 
> 2024-06-19T11:22:56,454  INFO [NotificationEventPoll 0]
> HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value:
> name=metast
> ore.batch.retrieve.max defaultValue=50 2024-06-19T11:23:01,656  INFO
> [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr
> cmd=scheduled_query_poll
> 2024-06-19T11:23:56,375  INFO [NotificationEventPoll 0]
> HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value:
> name=metast
> ore.batch.retrieve.max defaultValue=50 2024-06-19T11:24:01,946  INFO
> [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr
> cmd=scheduled_query_poll
> 2024-06-19T11:24:56,373  INFO [NotificationEventPoll 0]
> HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value:
> name=metast
> ore.batch.retrieve.max defaultValue=50 2024-06-19T11:25:02,197  INFO
> [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr
> cmd=scheduled_query_poll
> 2024-06-19T11:25:56,376  INFO [NotificationEventPoll 0]
> HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value:
> name=metast
> ore.batch.retrieve.max defaultValue=50 2024-06-19T11:26:02,390  INFO
> [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr
> cmd=scheduled_query_poll
> 2024-06-19T11:26:56,373  INFO [NotificationEventPoll 0]
> HiveMetaStore.audit: ugi=root ip=unknown-ip-addr cmd=get_config_value:
> name=metast
> ore.batch.retrieve.max defaultValue=50 2024-06-19T11:27:02,660  INFO
> [Scheduled Query Poller] HiveMetaStore.audit: ugi=root ip=unknown-ip-addr
> cmd=scheduled_query_poll
> 2024-06-19T11:27:48,645  INFO [00b77a5e-7cec-4e10-a0ae-f94450a56ab0
> HiveServer2-Handler-Pool: Thread-54] session.HiveSessionImpl: executing
> SELEC
> T emp.emp_id, emp.emp_name, dept.dept_nameFROM emp
> JOIN dept ON  emp.dept_id = dept.dept_id
> 2024-06-19T11:27:48,654  INFO 

Re: [VOTE] Mark Hive 2.x EOL

2024-05-10 Thread Denys Kuzmenko
+1 (binding)


Re: [Discussion] HIVE-28211: Restore hive-exec:core jar

2024-05-03 Thread Denys Kuzmenko
I agree that shaded hive-exec should be the proper way to go, however, ATM it's 
a show-stopper for many downstream projects to upgrade. 
Also based on the mail threads, they clearly understand the risks of using an 
unshaded jar but still insist on keeping it. 
If we'd like to improve the project acceptance, perhaps we could allow some 
flexibility. 


Re: [Discussion] HIVE-28211: Restore hive-exec:core jar

2024-05-01 Thread Denys Kuzmenko
Just found out that Amoro project is also using hive-exec:jar:core
+1 to restore


Re: [Discussion] HIVE-28211: Restore hive-exec:core jar

2024-04-29 Thread Denys Kuzmenko
Would we fix the problem by relocating just guava and joda-time? 
Here is how it's done in Impala:
https://github.com/apache/impala/blob/master/java/shaded-deps/hive-exec/pom.xml#L70-L77
 


Re: [DISCUS] Plan the next Hive release

2024-04-18 Thread Denys Kuzmenko
The idea is to cherry-pick individual bug fixes/improvements that could be 
easily tested to avoid a complete release test cycle (TPC-DS performance suite, 
multi-db tests, etc)

On 2024/04/18 11:22:09 Stamatis Zampetakis wrote:
> There are also many projects that never create minor version releases;
> it's up to each project to decide what fits best on each occasion.
> 
> I am not against minor releases nor suggest that this should be the
> way to go for every release from now onwards. I am just saying that at
> this point in time I don't see a big benefit to release from side
> branches.
> 
> Again the motivation for releasing early and often from master is that
> it has less maintenance overhead for the community and the end-users
> can benefit from all improvements as soon as possible. Certainly if we
> introduce breaking changes and big risky features this approach cannot
> work.
> 
> Anyways, I am glad that we are having this discussion and it's also
> very positive that we are talking about a new release in less than a
> month since 4.0.0 came out. No matter if it is 4.0.1 or 4.1.0 I am
> fully onboard and happy to help as much as I can :)
> 
> Best,
> Stamatis
> 
> On Thu, Apr 18, 2024 at 11:53 AM Denys Kuzmenko  wrote:
> >
> > Hi Stamatis,
> >
> > That is the standard practice to create minor version release for bugfixes. 
> > Many upstream projects follow that same strategy, check Iceberg for example.
> >
> > Regards,
> > Denys
> >
> > On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> > > The 4.0.0 release was quite recent so I assume we don't have major
> > > breaking changes in there at the moment so we could cut the release
> > > directly from master as soon as we want. HIVE-28166 is already merged
> > > so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.
> > >
> > > The experience shows that we are not very good at maintaining multiple
> > > release branches so in general I would prefer to focus on releasing
> > > only from master for the time being. Hive is a quite mature project so
> > > in principle breaking changes should be rather rare which gives us a
> > > bit of margin. I think a scheme where we backport less and release
> > > more is preferable.
> > >
> > > Best,
> > > Stamatis
> > >
> > > On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
> > > >
> > > > Hi Stamatis,
> > > > The plan is to have a release line cut from the branch-4.0, So, we plan 
> > > > to pull in some critical bug fixes & improvements into the 4.0.1 
> > > > release and have a quicker release.
> > > > As of now we are just putting the label "hive-4.0.1-must" on the 
> > > > tickets and we plan to make sure those get c-picked to the release 
> > > > line. AFAIK we haven't started committing to any branch yet, was 
> > > > waiting if anyone feels differently, so we can hold back if you have 
> > > > concerns or take a different approach as well.
> > > >
> > > > From CI you mean to say the daily builds? else if you create a PR 
> > > > targeting to branch-4.0, it will run the entire test suite I believe? 
> > > > In the meantime I will update the instructions regarding the target 
> > > > branch & the label if anyone wants that a particular ticket to be part 
> > > > of the 4.0.1 release.
> > > >
> > > > -Ayush
> > > >
> > > > On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  
> > > > wrote:
> > > >>
> > > >> Thanks for starting the discussion Ayush.
> > > >>
> > > >> Having frequent releases is definitely needed so we should keep the
> > > >> momentum going.
> > > >>
> > > >> I had the impression from other threads that the next Hive release
> > > >> would be 4.1.0 and that it would be cut from master. I would like to
> > > >> understand how 4.0.1 is different and if it is, what is the
> > > >> contribution pattern that contributors and committers should follow?
> > > >> If the idea is to maintain and commit in two (or more) branches the
> > > >> steps should be documented and CI should be running on those branches.
> > > >>
> > > >> Best,
> > > >> Stamatis
> > > >>
> > > >> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  
> > > >> wrote:
> > > >> >
> > > >> > We might need it sooner as identified some critical issues in the 
> > > >> > recent code:
> > > >> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name 
> > > >> > and operates on a main;
> > > >> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is 
> > > >> > broken;
> > >
> 


Re: [DISCUS] Plan the next Hive release

2024-04-18 Thread Denys Kuzmenko
Hi Stamatis,

That is the standard practice to create minor version release for bugfixes. 
Many upstream projects follow that same strategy, check Iceberg for example.

Regards,
Denys

On 2024/04/18 07:49:59 Stamatis Zampetakis wrote:
> The 4.0.0 release was quite recent so I assume we don't have major
> breaking changes in there at the moment so we could cut the release
> directly from master as soon as we want. HIVE-28166 is already merged
> so we could aim to cut 4.1.0 as soon as HIVE-28190 goes in.
> 
> The experience shows that we are not very good at maintaining multiple
> release branches so in general I would prefer to focus on releasing
> only from master for the time being. Hive is a quite mature project so
> in principle breaking changes should be rather rare which gives us a
> bit of margin. I think a scheme where we backport less and release
> more is preferable.
> 
> Best,
> Stamatis
> 
> On Wed, Apr 17, 2024 at 9:56 AM Ayush Saxena  wrote:
> >
> > Hi Stamatis,
> > The plan is to have a release line cut from the branch-4.0, So, we plan to 
> > pull in some critical bug fixes & improvements into the 4.0.1 release and 
> > have a quicker release.
> > As of now we are just putting the label "hive-4.0.1-must" on the tickets 
> > and we plan to make sure those get c-picked to the release line. AFAIK we 
> > haven't started committing to any branch yet, was waiting if anyone feels 
> > differently, so we can hold back if you have concerns or take a different 
> > approach as well.
> >
> > From CI you mean to say the daily builds? else if you create a PR targeting 
> > to branch-4.0, it will run the entire test suite I believe? In the meantime 
> > I will update the instructions regarding the target branch & the label if 
> > anyone wants that a particular ticket to be part of the 4.0.1 release.
> >
> > -Ayush
> >
> > On Wed, 17 Apr 2024 at 12:42, Stamatis Zampetakis  wrote:
> >>
> >> Thanks for starting the discussion Ayush.
> >>
> >> Having frequent releases is definitely needed so we should keep the
> >> momentum going.
> >>
> >> I had the impression from other threads that the next Hive release
> >> would be 4.1.0 and that it would be cut from master. I would like to
> >> understand how 4.0.1 is different and if it is, what is the
> >> contribution pattern that contributors and committers should follow?
> >> If the idea is to maintain and commit in two (or more) branches the
> >> steps should be documented and CI should be running on those branches.
> >>
> >> Best,
> >> Stamatis
> >>
> >> On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko  
> >> wrote:
> >> >
> >> > We might need it sooner as identified some critical issues in the recent 
> >> > code:
> >> > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name and 
> >> > operates on a main;
> >> > 2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;
> 


Re: Issue with joda-time library bundled in hive-exec:4.0.0

2024-04-16 Thread Denys Kuzmenko
Hi Ravi,

hive-exec is the uber jar, the same thing is done in Hive-3.x. We are 
considering restoring the hive-core jar that only has classes from ql

On 2024/04/16 06:24:20 Mergu Ravi wrote:
> Hi Hive Team,
> 
> I'm currently using the Hive 4.0.0 libraries and facing an issue with the
> hive-exec:4.0.0 library. It seems that the Joda-Time library is bundled
> within it, preventing me from excluding it and using my existing Joda-Time
> library. Could you please provide insight into why this bundling has been
> implemented? Additionally, is there any plan to unbundle the Joda-Time
> library in future releases?
> 
> -- 
> 
> Thanks & Regards,
> 
> 
> 
> Ravi Mergu
> SMTS-2
> o:  +91 40 64535355
> m: +91 9959618687
> w: www.gaiansolutions.com
> 
> 
> 
> 
> 
> *Please consider the environment before printing this email.* This message
> contains confidential information and is intended only for the individual
> named. If you are not the named addressee you should not disseminate,
> distribute or copy this e-mail
> 


Re: [DISCUS] Plan the next Hive release

2024-04-10 Thread Denys Kuzmenko
We might need it sooner as identified some critical issues in the recent code:
1. HIVE-28166: Truncate on Iceberg table disregards the branch name and 
operates on a main;
2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;


Re: [Blog] Apache Hive 4.0 Release blog for ASF M & P

2024-04-05 Thread Denys Kuzmenko
Looks great, thanks Ayush!


Re: HIVE-28059: Iceberg REST Catalog

2024-04-05 Thread Denys Kuzmenko
Hi Henri,

The idea to provide a simple, open standard interface to enable integration of 
3rd party compute engines and tools is great, however, there are concerns about 
the suggested design.

-1 on the current implementation (+1 more Jetty server on HMS instance)

org.apache.iceberg.rest.HMSCatalogServer
Server httpServer = new Server(port)

* Iceberg provides a pluggable catalog interface on the client side to manage 
table metadata for creating, altering, and dropping tables, allowing seamless 
integration with existing data systems. 

* We should not embed or tight RestCatalog to the HMS. It should be an 
independent component with a pluggable design (work with different data 
catalogs, such as Hive, Snowflake, Glue, etc.)

* Breaking down complex systems into independently deployable services improves 
scalability, flexibility, and maintenance simplicity.

Regards,
Denys






[ANNOUNCE] Apache Hive 4.0.0 Released

2024-03-29 Thread Denys Kuzmenko
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


[RESULT][VOTE] Release Apache Hive 4.0.0 (Release Candidate 0)

2024-03-29 Thread Denys Kuzmenko
Thanks to everyone who verified the release candidate and gave their
comments and votes.


Voting has closed and the results are as follows:


4 binding +1s:

* Ayush Saxena

* Denys Kuzmenko

* Marta Kuczora

* Krisztian Kasa

1 +0

* Stamatis Zampetakis


7 non-binding +1s:

* Butao Zhang

* Kirti Ruge

* Kokila Narayanan

* Simhadri Govindappa

* Sourabh Badhya

* Zhihua Deng

* Zoltán Rátkai

No -1s.


Therefore, I am delighted to announce that the proposal to release Apache
Hive 4.0.0 has passed.


I'll proceed with the next steps of the release and post an announcement
once the release becomes publicly available


Regards,

Denys


Re: [VOTE] Release Apache Hive 4.0.0 (Release Candidate 0)

2024-03-29 Thread Denys Kuzmenko
+1 (binding) 

* Executed functional test suite against Postgres DB


[VOTE] Release Apache Hive 4.0.0 (Release Candidate 0)

2024-03-26 Thread Denys Kuzmenko
Hi Everyone,

We would like to thank everyone who has contributed to the project and request
the Hive PMC members to review and vote on this new release candidate.

Apache Hive 4.0.0 RC-0 artifacts are available here:*
https://people.apache.org/~dkuzmenko/apache-hive-4.0.0-rc0/


The checksums are as follows:
- 83eb88549ae88d3df6a86bb3e2526c7f4a0f21acafe21452c18071cee058c666
apache-hive-4.0.0-bin.tar.gz
- 4dbc9321d245e7fd26198e5d3dff95e5f7d0673d54d0727787d72956a1bca4f5
apache-hive-4.0.0-src.tar.gz


You can find the KEYS file here:

* https://downloads.apache.org/hive/KEYS


A staged Maven repository URL is:*
https://repository.apache.org/content/repositories/orgapachehive-1127/

The git commit hash is:*
https://github.com/apache/hive/commit/183f8cb41d3dbed961ffd27999876468ff06690c


This corresponds to the tag: release-4.0.0-rc0
* https://github.com/apache/hive/tree/release-4.0.0-rc0

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PMC votes are cast.

(Only PMC members have binding votes, however, other community members
are encouraged to cast non-binding votes.)


[ ] +1 Release this package as Apache Hive 4.0.0
[ ] +0
[ ] -1 Do not release this because...


Please download, verify, and test.


Regards,

Denys


Re: Release of Hive 4 and TPC-DS benchmark

2024-03-19 Thread Denys Kuzmenko
Hi Pravin,

TPC-DS tracking Jira: HIVE-27929.

The functional test run is completed, waiting for the TPC-DS execution. There 
were some glitches with the infra last week, expecting results in the next 2-3 
days. After that, we should be ready with RC. 

Regards,
Denys


Re: Release of Hive 4 and TPC-DS benchmark

2024-03-01 Thread Denys Kuzmenko
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: Inquiry about Stable Release Timeline for Hive-Serde 4.X

2024-02-20 Thread Denys Kuzmenko
Hi Ravi,

ATM we have 3 items to resolve before the release [1]. 
1. HIVE-27924 will be merged in a couple of days;
2. HIVE-27775 is under review; 
3. HIVE-27858 is under investigation, however, we might exclude it from 4.0 
release;

In parallel, we are running TPC-DS benchmarks. 

Optimistically, we'll release 4.0 sometime next month.

Best,
Denys

[1] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20priority%20in%20(Critical%2C%20Blocker)%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20AND%20(affectedVersion%20in%20(4.0.0-alpha-1%2C%204.0.0-alpha-2%2C%204.0.0-beta-1%2C%204.0.0)%20%20and%20not%20affectedVersion%20in%20(3.1.0%2C%203.1.1%2C%203.1.2%2C%203.1.3)%20or%20affectedVersion%20%3D%20EMPTY)%20and%20created%20%3E%3D%20-52w%20ORDER%20BY%20created%20DESC


Re: [Discuss] Enable Attachments for Hive mailing lists

2024-01-24 Thread Denys Kuzmenko
+1


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

2024-01-17 Thread Denys Kuzmenko
+1 (binding)


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

2024-01-10 Thread Denys Kuzmenko
+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


[ANNOUNCE] Apache Hive 4.0.0 Branching

2023-12-01 Thread Denys Kuzmenko
Hi All,

Hive 4.0.0 release branch cut is happening today.

Best,
Denys


Re: Release of Hive 4 and TPC-DS benchmark

2023-11-23 Thread Denys Kuzmenko
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: [ANNOUNCE] New committer: Butao Zhang (zhangbutao)

2023-11-21 Thread Denys Kuzmenko
Congrats, very well deserved!


Re: Release of Hive 4 and TPC-DS benchmark

2023-11-07 Thread Denys Kuzmenko
Hi Sungwoo,

Thank you for bringing this up again.

Based on HIVE-26654, it looks like we have 3 PR pending review:
1. HIVE-26986 - Query 71
2. HIVE-27006 - Query 2
3. HIVE-27269 - Query 97 (is that ready to be reviewed?)

We'll prioritize those.

For query 14, as you suggested, we might set 
`hive.optimize.cte.materialize.threshold to -1` by default for now and fix it 
in the following releases.

Thanks,
Denys




Re: MiniHS2 and postgresql jars

2023-08-22 Thread Denys Kuzmenko
Instead of adding the dependencies, can't we add the possibility to include 
jdbc jars in the classpath?
something like this:

  org.apache.maven.plugins
  maven-failsafe-plugin
  

  
integration-test
verify
  

  
  


  
${itest.jdbc.jars}

   ...
  



Re: [VOTE] Release Apache Hive 4.0.0-beta-1 (Release Candidate 0)

2023-08-10 Thread Denys Kuzmenko
+1

* Verified signatures and checksum;
* Checked binary content and successfully built from the source;
* Skimmed through the release notes;
* Initialized backend DB schema and launched HMS & HS2 locally;
* Conducted basic checks via beeline:
- Created a few ACID & Iceberg tables and loaded data into them;
- Executed Select/Insert/Update/Delete/Merge/IOW queries.

Thanks, Stamatis for driving the release.

Regards,
Denys


Re: [DISCUSS] Automatic rerunning of failed tests in Hive Pre-commit

2023-06-12 Thread Denys Kuzmenko
I’ll second the above. We already have a number of flaky tests that would go 
undetected and just increase the build time.


Re: Blogs/Designs For Apache Hive

2023-06-07 Thread Denys Kuzmenko
Nice, tnx Ayush!


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-02 Thread Denys Kuzmenko
great, this is the current list of release managers:

4.0.0 Stamatis Zampetakis
4.1.0 Denys Kuzmenko
4.2.0 Sai Hemanth Gantasala

Should we keep the same RM order and just shift the releases or find a 
volunteer for the 4.0.0-beta release, WDYT? 




Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-05-31 Thread Denys Kuzmenko
Hi folks,

The master branch has many new features, bug fixes, and performance 
improvements since alpha-2. However, we still have several correctness bugs 
[HIVE-26654] and performance issues that should be eliminated before the GA. 

Could we consider doing a beta release to keep at least a 6-month release 
cadence and also show the community that 4.0.0 GA is the next stop?

Thanks,
Denys


Re: [DISCUSS] HIVE 4.0 GA Release Proposal

2023-03-23 Thread Denys Kuzmenko
Thanks, Sungwoo for running the TPC-DS benchmark. Do we know if the same level 
of performance degradation was present in 4.0.0-alpha1?

All: please use the `hive-4.0.0-must` label in a ticket if you think it's a 
show-stopper for the release.


Re: Release managers

2023-03-23 Thread Denys Kuzmenko
Hi, I can take the following one: 4.1.0


Re: [DISCUSS] Incremental and cadence predictable release activity for HIVE

2023-03-23 Thread Denys Kuzmenko
Sorry for being late to the party. I think what Kirti proposes would be good 
for the project and end-users. As mentioned, we could start with 2-3 releases 
per year, and once we improve on the process and automation (CI/CD) we could 
reevaluate.  


[jira] [Created] (HIVE-27160) Iceberg: Optimise delete (entire) data from table

2023-03-21 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-27160:
-

 Summary: Iceberg: Optimise delete (entire) data from table
 Key: HIVE-27160
 URL: https://issues.apache.org/jira/browse/HIVE-27160
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


Currently, in MOR mode, Hive creates "positional delete" files during deletes. 
With "Delete from ", the entire dataset in the table or partition is written as 
a "positional delete" file.

During the read operation, all these files are read again causing huge delay.

Proposal: apply "truncate" optimization in case of "delete *".



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


[jira] [Created] (HIVE-27155) Iceberg: Vectorize virtual columns

2023-03-20 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-27155:
-

 Summary: Iceberg: Vectorize virtual columns
 Key: HIVE-27155
 URL: https://issues.apache.org/jira/browse/HIVE-27155
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


Vectorization gets disabled at runtime with the following reason: 
{code}
Select expression for SELECT operator: Virtual column PARTITION__SPEC__ID is 
not supported
{code}



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


[jira] [Created] (HIVE-26995) Iceberg: Enhance time travel syntax with expressions

2023-01-26 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26995:
-

 Summary: Iceberg: Enhance time travel syntax with expressions
 Key: HIVE-26995
 URL: https://issues.apache.org/jira/browse/HIVE-26995
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-26873) Whiltelist iceberg configs for sql std authorization

2022-12-19 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26873:
-

 Summary: Whiltelist iceberg configs for sql std authorization 
 Key: HIVE-26873
 URL: https://issues.apache.org/jira/browse/HIVE-26873
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-26811) SharedWorkOptimizer: take the union of virtual columns in mergeable TableScan

2022-12-06 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26811:
-

 Summary: SharedWorkOptimizer: take the union of virtual columns in 
mergeable TableScan
 Key: HIVE-26811
 URL: https://issues.apache.org/jira/browse/HIVE-26811
 Project: Hive
  Issue Type: Bug
Reporter: Denys Kuzmenko






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


Re: gRPC Support in Hive Metastore

2022-11-18 Thread Denys Kuzmenko
Hi Cameron,

That's fine, however, I usually contribute to the original PR.
You could download github cli and checkout the branch via the following 
command: 
`gh pr checkout `, in your case it was 3534.

Unfortunately,  Epic is not on the list of supported issue types for the Hive 
project. I would recommend using the Feature type and adding subtasks.


Re: gRPC Support in Hive Metastore

2022-11-18 Thread Denys Kuzmenko
Hi Cameron, Rohan,

Are you still planning to contribute or need some help/support in terms of code 
review/etc. 
I've checked Rohan's PR, it looks good, but requires a rebase. 

Please let us know how we could help.

Kind regards,
Denys 


[ANNOUNCE] Apache Hive 4.0.0-alpha-2 Released

2022-11-16 Thread Denys Kuzmenko
The Apache Hive team is proud to announce the release of Apache Hive
version 4.0.0-alpha-2

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.

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

Hive 4.0.0-alpha-2 Release Notes are available
here:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351489=Html=12310843

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

Regards,

The Apache Hive Team


Re: [DISCUSS] Jira Public Signup Disabled

2022-11-15 Thread Denys Kuzmenko
Hi Stamatis,

Thanks for bringing it up! +1 to implement the same process


Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 1

2022-11-14 Thread Denys Kuzmenko
Hi Team,

Thanks to everyone who checked and voted!

The vote was *successful* with 3 +1s. I'll start the release process.

Kind regards,
Denys

On Sat, Nov 12, 2022 at 10:42 PM Ádám Szita  wrote:

> +1 for alpha-2 RC1,
>
> Verified signatures and checksums, checked binary content and source. I've
> built Hive from source and also tried out the artifacts in mini cluster.
> HMS DB initiated with the schema scripts provided, and I did create table,
> insert into, delete from and Iceberg rollback queries.
>
> Thanks for taking care of this, Denys.
>
> On 2022/11/12 10:19:43 dengzhhu653 wrote:
> > +1 (non-binding)
> >
> >
> > * Build from source/RAT check: OK;
> >
> > * Checksums are all good;
> >
> > * Start HiveServer2 and HMS using tarball with MySQL, Hadoop 3.3.1, Tez
> 0.10.2: OK;
> >
> > * Run some simple DDL and DML queries: OK.
> >
> >
> > Thank you for driving this release.
> > Zhihua
> > At 2022-11-12 07:18:47, "Ayush Saxena"  wrote:
> > >+1(non-binding)
> > >* Built from source
> > >* Verified Signatures
> > >* Verified Checksums
> > >* Skimmed through the release notes
> > >* Verified no diff with the git repo
> > >* Deployed using the binary(hadoop-3.3.1) and tried some basic queries
> > >
> > >Thanx Denys for driving the release, Good Luck!!!
> > >
> > >-Ayush
> > >
> > >> On 12-Nov-2022, at 4:16 AM, Alessandro Solimando <
> alessandro.solima...@gmail.com> wrote:
> > >>
> > >> +1 (non-binding)
> > >>
> > >> - verified gpg signature: OK
> > >> $ gpg --verify apache-hive-4.0.0-alpha-2-bin.tar.gz.asc
> > >> apache-hive-4.0.0-alpha-2-bin.tar.gz
> > >> gpg: Signature made Mon  7 Nov 19:04:05 2022 CET
> > >> gpg:using RSA key
> 50606DE1BDBD5CF862A595A907C5682DAFC73125
> > >> gpg:issuer "dkuzme...@apache.org"
> > >> gpg: Good signature from "Denys Kuzmenko (CODE SIGNING KEY) <
> > >> dkuzme...@apache.org>" [unknown]
> > >> gpg: WARNING: The key's User ID is not certified with a trusted
> signature!
> > >> gpg:  There is no indication that the signature belongs to the
> > >> owner.
> > >> Primary key fingerprint: 5060 6DE1 BDBD 5CF8 62A5  95A9 07C5 682D
> AFC7 3125
> > >>
> > >> $ gpg --verify apache-hive-4.0.0-alpha-2-src.tar.gz.asc
> > >> apache-hive-4.0.0-alpha-2-src.tar.gz
> > >> gpg: Signature made Mon  7 Nov 19:04:25 2022 CET
> > >> gpg:using RSA key
> 50606DE1BDBD5CF862A595A907C5682DAFC73125
> > >> gpg:issuer "dkuzme...@apache.org"
> > >> gpg: Good signature from "Denys Kuzmenko (CODE SIGNING KEY) <
> > >> dkuzme...@apache.org>" [unknown]
> > >> gpg: WARNING: The key's User ID is not certified with a trusted
> signature!
> > >> gpg:  There is no indication that the signature belongs to the
> > >> owner.
> > >> Primary key fingerprint: 5060 6DE1 BDBD 5CF8 62A5  95A9 07C5 682D
> AFC7 3125
> > >>
> > >> - verified package checksum: OK
> > >> $ diff <(cat apache-hive-4.0.0-alpha-2-src.tar.gz.sha256) <(shasum -a
> 256
> > >> apache-hive-4.0.0-alpha-2-src.tar.gz)
> > >> $ diff <(cat apache-hive-4.0.0-alpha-2-bin.tar.gz.sha256) <(shasum -a
> 256
> > >> apache-hive-4.0.0-alpha-2-bin.tar.gz)
> > >>
> > >> - build with “mvn clean install -Piceberg -DskipTests” (from both the
> > >> branch and the src folder): OK
> > >> - checked release notes: OK
> > >> - checked few modules in Nexus: OK
> > >> - checking difference in folder: OK
> > >> $ diff -qr . ~/git/hive
> > >> (nothing worth mentioning)
> > >>
> > >> - environment used:
> > >> $ sw_vers
> > >> ProductName: macOS
> > >> ProductVersion: 11.6.8
> > >> BuildVersion: 20G730
> > >>
> > >> $ mvn --version
> > >> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> > >> Maven home: .../.sdkman/candidates/maven/current
> > >> Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime:
> > >> .../.sdkman/candidates/java/8.0.292.hs-adpt/jre
> > >> Default locale: en_IE, platform encoding: UTF-8
> > >> OS name: "mac os x", version: "10.16", arch: "x

Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 1

2022-11-07 Thread Denys Kuzmenko
UPD: Voting will conclude in 1 week (Monday 14th).


On Mon, Nov 7, 2022 at 7:57 PM Denys Kuzmenko 
wrote:

> Hi team,
>
> Let's give it 1 more chance.
>
> Apache Hive 4.0.0-alpha-2 Release Candidate 1 is available 
> here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc1/
>
>
> Change log:
>
> - Updated copyright notices (year of distribution was taken from 
> `project.build.outputTimestamp` defined in apache root pom)
>
> - javadoc artifacts included in maven staging repo
>
>
> The checksums are these:
> - f94c773e7ae3328d780138d9259c584e94d8f2e34715776cdfaaa78bcf3f25e1  
> apache-hive-4.0.0-alpha-2-bin.tar.gz
> - 02dbc19f007cb87e725713c67f69836b3efb8ffeb1562aac1f9c869e4429cc36  
> apache-hive-4.0.0-alpha-2-src.tar.gz
>
>
> Maven artifacts are available 
> here:https://repository.apache.org/content/repositories/orgapachehive-1118/
>
> The tag release-4.0.0-alpha-2-rc1 has been created for this RC, you can find 
> it at
> https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc1
>
> The git commit hash 
> is:https://github.com/apache/hive/commit/36f5d91acb0fac00a5d46049bd45b744fe9aaab6
>
> Voting will conclude in 1 week (Monday 21th).
>
> Hive PMC Members: Please test and vote.
>
> Thanks,
>
> Denys
>
>


[VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 1

2022-11-07 Thread Denys Kuzmenko
Hi team,

Let's give it 1 more chance.

Apache Hive 4.0.0-alpha-2 Release Candidate 1 is available
here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc1/


Change log:

- Updated copyright notices (year of distribution was taken from
`project.build.outputTimestamp` defined in apache root pom)

- javadoc artifacts included in maven staging repo


The checksums are these:
- f94c773e7ae3328d780138d9259c584e94d8f2e34715776cdfaaa78bcf3f25e1
apache-hive-4.0.0-alpha-2-bin.tar.gz
- 02dbc19f007cb87e725713c67f69836b3efb8ffeb1562aac1f9c869e4429cc36
apache-hive-4.0.0-alpha-2-src.tar.gz


Maven artifacts are available
here:https://repository.apache.org/content/repositories/orgapachehive-1118/

The tag release-4.0.0-alpha-2-rc1 has been created for this RC, you
can find it at
https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc1

The git commit hash
is:https://github.com/apache/hive/commit/36f5d91acb0fac00a5d46049bd45b744fe9aaab6

Voting will conclude in 1 week (Monday 21th).

Hive PMC Members: Please test and vote.

Thanks,

Denys


[jira] [Created] (HIVE-26704) Cleaner shouldn't be blocked by global min open txnId

2022-11-03 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26704:
-

 Summary: Cleaner shouldn't be blocked by global min open txnId
 Key: HIVE-26704
 URL: https://issues.apache.org/jira/browse/HIVE-26704
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[CANCEL][VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-31 Thread Denys Kuzmenko
Hi team,

Thank you for taking time to verify this RC!
Unfortunately, we didn't get enough votes to go ahead with the release.

Closing this vote as unsuccessful.

Kind regards,
Denys


Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-29 Thread Denys Kuzmenko
Hi team,

Thank you for taking time to verify this RC!
Unfortunately, we didn't get enough votes to go ahead with the release.

Closing this vote as unsuccessful.

Kind regards,
Denys

On Fri, Oct 28, 2022, 15:56 Stamatis Zampetakis  wrote:

> I think that having a proper NOTICE file in jars is important to comply
> with the ASF release policy:
> * https://www.apache.org/legal/release-policy.html#licensing-documentation
> * https://www.apache.org/legal/src-headers.html#notice
> * https://www.apache.org/legal/src-headers.html#faq-binaries
> The fact that the NOTICE wasn't updated in alpha-1 is most likely an
> oversight.
>
> Having said that the final decision is up to the release manager.
>
> Best,
> Stamatis
>
> On Fri, Oct 28, 2022 at 1:57 PM Denys Kuzmenko
>  wrote:
>
> > Hi Stamatis,
> >
> > My bad, sorry. Removed the ".imp" files and updated the release
> artifacts.*
> > *** NO CODE CHANGES 
> > I was following the alpha-1 release and the NOTICE wasn't updated there
> as
> > well. I don't think that should be a blocker. Noted that + javadoc
> > artifacts for the new RC.
> >
> > fc7908f40ec854671c6795acb525649d83c071d70cf62961dc90a251a0f45e47
> >  apache-hive-4.0.0-alpha-2-bin.tar.gz
> > f2814aadeca56ad1d8d9f7797b99d1670f6450f68ff6cae829384c9c102cd7a9
> >  apache-hive-4.0.0-alpha-2-src.tar.gz
> >
> > Thanks,
> > Denys
> >
> > On Fri, Oct 28, 2022 at 12:28 PM Stamatis Zampetakis 
> > wrote:
> >
> > > -1 (non-binding)
> > >
> > > Ubuntu 20.04.5 LTS, java version "1.8.0_261", Apache Maven 3.6.3
> > >
> > > * Verified signatures and checksums OK
> > > * Checked diff between git repo and release sources (diff -qr hive-git
> > > hive-src) KO (among other *.iml files present in release sources but
> not
> > in
> > > git)
> > > * Checked LICENSE, NOTICE, and README.md file OK
> > > * Built from release sources (mvn clean install -DskipTests -Pitests)
> OK
> > > * Package binaries from release sources (mvn clean package -DskipTests)
> > OK
> > > * Built from git tag (mvn clean install -DskipTests -Pitests) OK
> > > * Run smoke tests on pseudo cluster using hive-dev-box [1] OK
> > > * Spot check maven artifacts for general structure, LICENSE, NOTICE,
> > > META-INF content KO (NOTICE file in hive-exec-4.0.0-alpha-2.jar has
> > > copyright for 2020)
> > >
> > > Smoke tests included: * Derby metastore initialization * simple CREATE
> > > TABLE statements; * basic INSERT INTO VALUES statements; * basic SELECT
> > > statements with simple INNER JOIN, WHERE, and GROUP BY variations; *
> > > EXPLAIN statement variations; * ANALYZE TABLE variations;
> > >
> > > The negative vote is for the spurious *.iml (IntelliJ project) files
> > > present in the release sources and the outdated NOTICE file in maven
> > > artifacts).
> > >
> > > Also javadoc artifacts are missing from maven staging repo. I checked
> > > previous releases and it seems that they were not there as well so this
> > is
> > > not blocking but may be worth fixing for the next release.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://lists.apache.org/thread/7yqs7o6ncpottqx8txt0dtt9858ypsbb
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachehive-1117/org/apache/hive/hive-exec/4.0.0-alpha-2/hive-exec-4.0.0-alpha-2.jar
> > >
> > > On Fri, Oct 28, 2022 at 10:32 AM Ayush Saxena 
> > wrote:
> > >
> > > > +1 (non-binding)
> > > > * Built from source.
> > > > * Verified Checksums.
> > > > * Verified Signatures
> > > > * Ran some basic unit tests.
> > > > * Ran some basic ACID & Iceberg related queries with Tez.
> > > > * Skimmed through the Maven Artifacts, Looks Good.
> > > >
> > > > Thanx Denys for driving the release. Good Luck!!!
> > > >
> > > > -Ayush
> > > >
> > > > On Fri, 28 Oct 2022 at 13:46, Denys Kuzmenko  > > > .invalid>
> > > > wrote:
> > > >
> > > > > Extending voting for 24hr. 1 more +1 is needed from the PMC to
> > promote
> > > > the
> > > > > release.
> > > > > If not given, I'll be closing this vote as unsuccessful.
> > > > >
> > > > > On Thu, Oct 27, 2022 at 11:16 PM Chris Nauroth <
> cnaur...@apache.org>
> > > > > wrote:
> &g

Re: Updating Wiki about Hikari Configuration Properties

2022-10-29 Thread Denys Kuzmenko
Hi Chris,

Previously I just gave you edit permissions for the requested page, but now
granted Hive space permissions. Please check again and let me know.

On Fri, Oct 28, 2022 at 7:51 PM Chris Nauroth  wrote:

> Thank you, Denys. Unfortunately, I still don't see the Edit button like I
> do on other projects where I have access (Hadoop, Zookeeper). I just
> realized my Confluence login is actually just "cnauroth", so maybe I caused
> some confusion by stating it as "cnaur...@apache.org"?
>
> Ayush, to further clarify, yes, I am planning to backport HIVE-17317 onto
> versions 3.1.2 and 3.1.3 of Dataproc's Hive distro. I've already tested
> locally and confirmed that I can use hikaricp.minimumIdle to limit the
> number of connections. I'd also be happy to send an upstream pull request
> against branch-3.1 for the backport if the community would find that
> valuable. Let me know.
>
> When I make the Confluence edit, I'll clarify which versions have this
> support.
>
> Chris Nauroth
>
>
> On Fri, Oct 28, 2022 at 4:37 AM Ayush Saxena  wrote:
>
> > Hi Chris,
> >
> > Just curious:
> >>
> >> BTW, the reason I discovered this is that I recently upgraded a cluster
> >> from Hive 2.x (default BoneCP) to Hive 3.x (default HikariCP).
> >
> >
> > As you said the prefix change happened in HIVE-17317 which is in
> > 4.0.0-alpha-1 [1] and you migrated to Hive 3.x, Then how did you face
> > this problem? Some patched version of Hive, or some missing FixVersion in
> > the Jira?
> >
> > Good to mention the version post which the change in prefix happens in
> the
> > wiki as well, to avoid future confusions due to versions.
> >
> > -Ayush
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-17317
> >
> > On Fri, 28 Oct 2022 at 17:02, Denys Kuzmenko
> >  wrote:
> >
> >> Hi Chris,
> >>
> >> Please try now
> >>
> >> On Fri, Oct 28, 2022 at 12:43 PM Stamatis Zampetakis  >
> >> wrote:
> >>
> >> > Hive PMC members can provide edit rights to the wiki.
> >> >
> >> > @Naveen, Dennys, Adam: Can someone please give write privileges to
> >> Chris?
> >> >
> >> > Best,
> >> > Stamatis
> >> >
> >> > On Fri, Oct 28, 2022 at 8:41 AM Chris Nauroth 
> >> wrote:
> >> >
> >> > > Hi everyone,
> >> > >
> >> > > Regarding this page:
> >> > >
> >> > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/hive/configuration+properties#ConfigurationProperties-HiveMetastoreConnectionPoolingConfiguration
> >> > >
> >> > > It states that the metastore's Hikari connection pool can be
> >> configured
> >> > by
> >> > > specifying properties prefixed as "hikari". This is not quite
> >> correct. In
> >> > > HIVE-17317, there was a bug fix made to the Hikari integration such
> >> that
> >> > > the proper prefix is "hikaricp". For example:
> >> > >
> >> > >   
> >> > > hikaricp.minimumIdle
> >> > > 4
> >> > > false
> >> > > Dataproc Cluster Properties
> >> > >   
> >> > >
> >> > > Could you please grant access to me (cnaur...@apache.org) to update
> >> the
> >> > > page? If you prefer not to grant access, could a Hive committer make
> >> the
> >> > > change for me?
> >> > >
> >> > > BTW, the reason I discovered this is that I recently upgraded a
> >> cluster
> >> > > from Hive 2.x (default BoneCP) to Hive 3.x (default HikariCP). After
> >> the
> >> > > upgrade, I found that HiveMetaStore was generating far more database
> >> > > connections at baseline, putting extra burden on the database. It
> >> appears
> >> > > that BoneCP default behavior (4 idle connections) is different from
> >> > > HikariCP default behavior (idle connections equal to max connections
> >> > which
> >> > > is 10). This put me down the path of wanting to control Hikari's
> >> > > minimumIdle setting and then finding this discrepancy in the
> >> > documentation.
> >> > >
> >> > > Passing on this information in case others are seeing unusually high
> >> > > connection counts after an upgrade to 3.x.
> >> > >
> >> > > Chris Nauroth
> >> > >
> >> >
> >>
> >
>


Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-28 Thread Denys Kuzmenko
Hi Stamatis,

My bad, sorry. Removed the ".imp" files and updated the release artifacts.*
*** NO CODE CHANGES 
I was following the alpha-1 release and the NOTICE wasn't updated there as
well. I don't think that should be a blocker. Noted that + javadoc
artifacts for the new RC.

fc7908f40ec854671c6795acb525649d83c071d70cf62961dc90a251a0f45e47
 apache-hive-4.0.0-alpha-2-bin.tar.gz
f2814aadeca56ad1d8d9f7797b99d1670f6450f68ff6cae829384c9c102cd7a9
 apache-hive-4.0.0-alpha-2-src.tar.gz

Thanks,
Denys

On Fri, Oct 28, 2022 at 12:28 PM Stamatis Zampetakis 
wrote:

> -1 (non-binding)
>
> Ubuntu 20.04.5 LTS, java version "1.8.0_261", Apache Maven 3.6.3
>
> * Verified signatures and checksums OK
> * Checked diff between git repo and release sources (diff -qr hive-git
> hive-src) KO (among other *.iml files present in release sources but not in
> git)
> * Checked LICENSE, NOTICE, and README.md file OK
> * Built from release sources (mvn clean install -DskipTests -Pitests) OK
> * Package binaries from release sources (mvn clean package -DskipTests) OK
> * Built from git tag (mvn clean install -DskipTests -Pitests) OK
> * Run smoke tests on pseudo cluster using hive-dev-box [1] OK
> * Spot check maven artifacts for general structure, LICENSE, NOTICE,
> META-INF content KO (NOTICE file in hive-exec-4.0.0-alpha-2.jar has
> copyright for 2020)
>
> Smoke tests included: * Derby metastore initialization * simple CREATE
> TABLE statements; * basic INSERT INTO VALUES statements; * basic SELECT
> statements with simple INNER JOIN, WHERE, and GROUP BY variations; *
> EXPLAIN statement variations; * ANALYZE TABLE variations;
>
> The negative vote is for the spurious *.iml (IntelliJ project) files
> present in the release sources and the outdated NOTICE file in maven
> artifacts).
>
> Also javadoc artifacts are missing from maven staging repo. I checked
> previous releases and it seems that they were not there as well so this is
> not blocking but may be worth fixing for the next release.
>
> Best,
> Stamatis
>
> [1] https://lists.apache.org/thread/7yqs7o6ncpottqx8txt0dtt9858ypsbb
>
> https://repository.apache.org/content/repositories/orgapachehive-1117/org/apache/hive/hive-exec/4.0.0-alpha-2/hive-exec-4.0.0-alpha-2.jar
>
> On Fri, Oct 28, 2022 at 10:32 AM Ayush Saxena  wrote:
>
> > +1 (non-binding)
> > * Built from source.
> > * Verified Checksums.
> > * Verified Signatures
> > * Ran some basic unit tests.
> > * Ran some basic ACID & Iceberg related queries with Tez.
> > * Skimmed through the Maven Artifacts, Looks Good.
> >
> > Thanx Denys for driving the release. Good Luck!!!
> >
> > -Ayush
> >
> > On Fri, 28 Oct 2022 at 13:46, Denys Kuzmenko  > .invalid>
> > wrote:
> >
> > > Extending voting for 24hr. 1 more +1 is needed from the PMC to promote
> > the
> > > release.
> > > If not given, I'll be closing this vote as unsuccessful.
> > >
> > > On Thu, Oct 27, 2022 at 11:16 PM Chris Nauroth 
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > * Verified all checksums.
> > > > * Verified all signatures.
> > > > * Built from source.
> > > > * mvn clean install -Piceberg -DskipTests
> > > > * Tests passed.
> > > > * mvn --fail-never clean verify -Piceberg -Pitests
> > > > -Dmaven.test.jvm.args='-Xmx2048m -DJETTY_AVAILABLE_PROCESSORS=4'
> > > >
> > > > I figured out why my test runs were failing in HTTP server
> > > initialization.
> > > > Jetty enforces thread leasing to warn or abort if there aren't enough
> > > > threads available [1]. During startup, it attempts to lease a thread
> > per
> > > > NIO selector [2]. By default, the number of NIO selectors to use is
> > > > determined based on available CPUs [3]. This is mostly a passthrough
> to
> > > > Runtime.availableProcessors() [4]. In my case, running on a machine
> > with
> > > 16
> > > > CPUs, this ended up creating more than 4 selectors, therefore
> requiring
> > > > more than 4 threads and violating the lease check. I was able to work
> > > > around this by passing the JETTY_AVAILABLE_PROCESSORS system property
> > to
> > > > constrain the number of CPUs available to Jetty.
> > > >
> > > > If we are intentionally constraining the pool to 4 threads during
> > itests,
> > > > then would it also make sense to limit JETTY_AVAILABLE_PROCESSORS in
> > > > maven.test.jvm.args of the root pom.xml, so that others don't ru

Re: Updating Wiki about Hikari Configuration Properties

2022-10-28 Thread Denys Kuzmenko
Hi Chris,

Please try now

On Fri, Oct 28, 2022 at 12:43 PM Stamatis Zampetakis 
wrote:

> Hive PMC members can provide edit rights to the wiki.
>
> @Naveen, Dennys, Adam: Can someone please give write privileges to Chris?
>
> Best,
> Stamatis
>
> On Fri, Oct 28, 2022 at 8:41 AM Chris Nauroth  wrote:
>
> > Hi everyone,
> >
> > Regarding this page:
> >
> >
> >
> https://cwiki.apache.org/confluence/display/hive/configuration+properties#ConfigurationProperties-HiveMetastoreConnectionPoolingConfiguration
> >
> > It states that the metastore's Hikari connection pool can be configured
> by
> > specifying properties prefixed as "hikari". This is not quite correct. In
> > HIVE-17317, there was a bug fix made to the Hikari integration such that
> > the proper prefix is "hikaricp". For example:
> >
> >   
> > hikaricp.minimumIdle
> > 4
> > false
> > Dataproc Cluster Properties
> >   
> >
> > Could you please grant access to me (cnaur...@apache.org) to update the
> > page? If you prefer not to grant access, could a Hive committer make the
> > change for me?
> >
> > BTW, the reason I discovered this is that I recently upgraded a cluster
> > from Hive 2.x (default BoneCP) to Hive 3.x (default HikariCP). After the
> > upgrade, I found that HiveMetaStore was generating far more database
> > connections at baseline, putting extra burden on the database. It appears
> > that BoneCP default behavior (4 idle connections) is different from
> > HikariCP default behavior (idle connections equal to max connections
> which
> > is 10). This put me down the path of wanting to control Hikari's
> > minimumIdle setting and then finding this discrepancy in the
> documentation.
> >
> > Passing on this information in case others are seeing unusually high
> > connection counts after an upgrade to 3.x.
> >
> > Chris Nauroth
> >
>


Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-28 Thread Denys Kuzmenko
> > [2]
> > >
> >
> https://github.com/apache/hive/blob/release-4.0.0-alpha-2-rc0/pom.xml#L197
> > > [3] https://issues.apache.org/jira/browse/HADOOP-16196
> > >
> > > On Thu, 27 Oct 2022 at 23:15, Alessandro Solimando <
> > > alessandro.solima...@gmail.com> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > unfortunately my vote is -1 (although non-binding) due to a classpath
> > > error
> > > > which prevents queries involving Tez to complete (all the details at
> > the
> > > > end of the email, apologies for the lengthy text but I wanted to
> > provide
> > > > all the context).
> > > >
> > > > - verified gpg signature: OK
> > > >
> > > > $ wget https://www.apache.org/dist/hive/KEYS
> > > >
> > > > $ gpg --import KEYS
> > > >
> > > > ...
> > > >
> > > > $ gpg --verify apache-hive-4.0.0-alpha-2-bin.tar.gz.asc
> > > > apache-hive-4.0.0-alpha-2-bin.tar.gz
> > > >
> > > > gpg: Signature made Thu 27 Oct 15:11:48 2022 CEST
> > > >
> > > > gpg:using RSA key
> > > 50606DE1BDBD5CF862A595A907C5682DAFC73125
> > > >
> > > > gpg:issuer "dkuzme...@apache.org"
> > > >
> > > > gpg: Good signature from "Denys Kuzmenko (CODE SIGNING KEY) <
> > > > dkuzme...@apache.org>" [unknown]
> > > >
> > > > gpg: WARNING: The key's User ID is not certified with a trusted
> > > signature!
> > > >
> > > > gpg:  There is no indication that the signature belongs to
> the
> > > > owner.
> > > >
> > > > Primary key fingerprint: 5060 6DE1 BDBD 5CF8 62A5  95A9 07C5 682D
> AFC7
> > > 3125
> > > >
> > > > $ gpg --verify apache-hive-4.0.0-alpha-2-src.tar.gz.asc
> > > > apache-hive-4.0.0-alpha-2-src.tar.gz
> > > >
> > > > gpg: Signature made Thu 27 Oct 15:12:08 2022 CEST
> > > >
> > > > gpg:using RSA key
> > > 50606DE1BDBD5CF862A595A907C5682DAFC73125
> > > >
> > > > gpg:issuer "dkuzme...@apache.org"
> > > >
> > > > gpg: Good signature from "Denys Kuzmenko (CODE SIGNING KEY) <
> > > > dkuzme...@apache.org>" [unknown]
> > > >
> > > > gpg: WARNING: The key's User ID is not certified with a trusted
> > > signature!
> > > >
> > > > gpg:  There is no indication that the signature belongs to
> the
> > > > owner.
> > > >
> > > > Primary key fingerprint: 5060 6DE1 BDBD 5CF8 62A5  95A9 07C5 682D
> AFC7
> > > 3125
> > > >
> > > > (AFAIK, this warning is OK)
> > > >
> > > > - verified package checksum: OK
> > > >
> > > > $ diff <(cat apache-hive-4.0.0-alpha-2-src.tar.gz.sha256) <(shasum -a
> > 256
> > > > apache-hive-4.0.0-alpha-2-src.tar.gz)
> > > >
> > > > $ diff <(cat apache-hive-4.0.0-alpha-2-bin.tar.gz.sha256) <(shasum -a
> > 256
> > > > apache-hive-4.0.0-alpha-2-bin.tar.gz)
> > > >
> > > > - verified maven build (no tests): OK
> > > >
> > > > $ mvn clean install -DskipTests
> > > >
> > > > ...
> > > >
> > > > [INFO]
> > > >
> > 
> > > >
> > > > [INFO] BUILD SUCCESS
> > > >
> > > > [INFO]
> > > >
> > 
> > > >
> > > > [INFO] Total time:  04:31 min
> > > >
> > > > - checked release notes: OK
> > > >
> > > > - checked few modules in Nexus: OK
> > > >
> > > > - environment used:
> > > >
> > > > $ sw_vers
> > > >
> > > > ProductName: macOS
> > > >
> > > > ProductVersion: 11.6.8
> > > >
> > > > BuildVersion: 20G730
> > > >
> > > > $ mvn --version
> > > >
> > > > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> > > >
> > > > Maven home: .../.sdkman/candidates/maven/current
> > > >
> > > > Java version:

Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-27 Thread Denys Kuzmenko
Hi Alessandro,

There were no code changes, just missing artifacts due to an outdated
release guide (iceberg bits are generated only under iceberg profile).
Not sure that we should create new RC in that case. Naveen, what
do you think?


On Thu, Oct 27, 2022 at 3:30 PM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:

> Hi Denys,
> in other Apache communities I generally see that votes are cancelled and a
> new RC is prepared when there are changes or blocking issues like in this
> case, not sure how things are done in Hive though.
>
> Best regards,
> Alessandro
>
> On Thu, 27 Oct 2022 at 15:22, Denys Kuzmenko  .invalid>
> wrote:
>
> > Hi Adam,
> >
> > Thanks for pointing that out! Upstream release guide is outdated. Once I
> > receive the edit rights, I'll amend the instructions.
> > Updated the release artifacts and checksums:
> >
> > Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
> > here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/
> >
> >
> > The checksums are these:
> > - b4dbaac5530694f631af13677ffe5443addc148bd94176b27a109a6da67f5e0f
> > apache-hive-4.0.0-alpha-2-bin.tar.gz
> > - 8c4639915e9bf649f4a55cd9adb9d266aa15d8fa48ddfadb28ebead2c0aee4d0
> > apache-hive-4.0.0-alpha-2-src.tar.gz
> >
> > Maven artifacts are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachehive-1117/
> >
> > The tag release-4.0.0-alpha-2-rc0 has been applied to the source for
> > this release in github, you can see it at
> > https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc0
> >
> > The git commit hash
> > is:
> >
> https://github.com/apache/hive/commit/da146200e003712e324496bf560a1702485d231c
> >
> >
> > Please check again.
> >
> >
> > Thanks,
> > Denys
> >
> > On Thu, Oct 27, 2022 at 2:53 PM Ádám Szita  wrote:
> >
> > > Hi Denys,
> > >
> > > Unfortutantely I can't give a plus 1 on this yet, as the Iceberg
> > artifacts
> > > are missing from the binary tar.gz. Perhaps -Piceberg flag was missing
> > > during build, can you please rebuild?
> > >
> > > Thanks,
> > > Adam
> > >
> > > On 2022/10/25 11:20:23 Denys Kuzmenko wrote:
> > > > Hi team,
> > > >
> > > >
> > > > Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
> > > > here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/
> > > >
> > > >
> > > > The checksums are these:
> > > > - 7d4c54ecfe2b04cabc283a84defcc1e8a02eed0e13baba2a2c91ae882b6bfaf7
> > > > apache-hive-4.0.0-alpha-2-bin.tar.gz
> > > > - 8c4639915e9bf649f4a55cd9adb9d266aa15d8fa48ddfadb28ebead2c0aee4d0
> > > > apache-hive-4.0.0-alpha-2-src.tar.gz
> > > >
> > > > Maven artifacts are available
> > > > here:
> > > https://repository.apache.org/content/repositories/orgapachehive-1117/
> > > >
> > > > The tag release-4.0.0-alpha-2-rc0 has been applied to the source for
> > > > this release in github, you can see it at
> > > > https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc0
> > > >
> > > > The git commit hash
> > > > is:
> > >
> >
> https://github.com/apache/hive/commit/da146200e003712e324496bf560a1702485d231c
> > > >
> > > > Voting will conclude in 72 hours.
> > > >
> > > > Hive PMC Members: Please test and vote.
> > > >
> > > > Thanks
> > > >
> > >
> >
>


Re: [VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-27 Thread Denys Kuzmenko
Hi Adam,

Thanks for pointing that out! Upstream release guide is outdated. Once I
receive the edit rights, I'll amend the instructions.
Updated the release artifacts and checksums:

Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/


The checksums are these:
- b4dbaac5530694f631af13677ffe5443addc148bd94176b27a109a6da67f5e0f
apache-hive-4.0.0-alpha-2-bin.tar.gz
- 8c4639915e9bf649f4a55cd9adb9d266aa15d8fa48ddfadb28ebead2c0aee4d0
apache-hive-4.0.0-alpha-2-src.tar.gz

Maven artifacts are available
here:https://repository.apache.org/content/repositories/orgapachehive-1117/

The tag release-4.0.0-alpha-2-rc0 has been applied to the source for
this release in github, you can see it at
https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc0

The git commit hash
is:https://github.com/apache/hive/commit/da146200e003712e324496bf560a1702485d231c


Please check again.


Thanks,
Denys

On Thu, Oct 27, 2022 at 2:53 PM Ádám Szita  wrote:

> Hi Denys,
>
> Unfortutantely I can't give a plus 1 on this yet, as the Iceberg artifacts
> are missing from the binary tar.gz. Perhaps -Piceberg flag was missing
> during build, can you please rebuild?
>
> Thanks,
> Adam
>
> On 2022/10/25 11:20:23 Denys Kuzmenko wrote:
> > Hi team,
> >
> >
> > Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
> > here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/
> >
> >
> > The checksums are these:
> > - 7d4c54ecfe2b04cabc283a84defcc1e8a02eed0e13baba2a2c91ae882b6bfaf7
> > apache-hive-4.0.0-alpha-2-bin.tar.gz
> > - 8c4639915e9bf649f4a55cd9adb9d266aa15d8fa48ddfadb28ebead2c0aee4d0
> > apache-hive-4.0.0-alpha-2-src.tar.gz
> >
> > Maven artifacts are available
> > here:
> https://repository.apache.org/content/repositories/orgapachehive-1117/
> >
> > The tag release-4.0.0-alpha-2-rc0 has been applied to the source for
> > this release in github, you can see it at
> > https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc0
> >
> > The git commit hash
> > is:
> https://github.com/apache/hive/commit/da146200e003712e324496bf560a1702485d231c
> >
> > Voting will conclude in 72 hours.
> >
> > Hive PMC Members: Please test and vote.
> >
> > Thanks
> >
>


[VOTE] Apache Hive 4.0.0-alpha-2 Release Candidate 0

2022-10-25 Thread Denys Kuzmenko
Hi team,


Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/


The checksums are these:
- 7d4c54ecfe2b04cabc283a84defcc1e8a02eed0e13baba2a2c91ae882b6bfaf7
apache-hive-4.0.0-alpha-2-bin.tar.gz
- 8c4639915e9bf649f4a55cd9adb9d266aa15d8fa48ddfadb28ebead2c0aee4d0
apache-hive-4.0.0-alpha-2-src.tar.gz

Maven artifacts are available
here:https://repository.apache.org/content/repositories/orgapachehive-1117/

The tag release-4.0.0-alpha-2-rc0 has been applied to the source for
this release in github, you can see it at
https://github.com/apache/hive/tree/release-4.0.0-alpha-2-rc0

The git commit hash
is:https://github.com/apache/hive/commit/da146200e003712e324496bf560a1702485d231c

Voting will conclude in 72 hours.

Hive PMC Members: Please test and vote.

Thanks


Re: [Branching] Apache Hive 4.0.0-alpha-2 Release

2022-10-20 Thread Denys Kuzmenko
Hi Stamatis,

If you have an automatic script for that please run it.

Note, I saw tickets with `fixVersion = 4.0.0 and fixVersion =
4.0.0-alpha-2` in resolved state as well.
https://issues.apache.org/jira/browse/HIVE-26643?jql=project%20%3D%20HIVE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20in%20(4.0.0)%20AND%20fixVersion%20in%20(4.0.0-alpha-2)

Regards,
Denys

On Thu, Oct 20, 2022 at 11:26 AM Stamatis Zampetakis 
wrote:

> Hi everyone,
>
> The past discussions around the version used in JIRA can be found in the
> following threads [1, 2].
>
> As Ayush mentioned there are ~3K resolved tickets with Fix Version 4.0.0
> but most of them are also tagged with 4.0.0-alpha1 [3].
>
> I can easily remove the 4.0.0 tag from those tickets and keep only
> 4.0.0-alpha1 in Fix Version using bulk update; we can treat the
> remaining cases afterwards.
> Let me know if you want me to proceed with this change or if you have
> other suggestions.
>
> Best,
> Stamatis
>
> [1] https://lists.apache.org/thread/13w1s029b6gbych56zhzvj4x2vbv8k8q
> [2] https://the-asf.slack.com/archives/CFSSP9UPJ/p1646216936802329
> [3] project = hive and status = resolved and fixVersion = 4.0.0 and
> fixVersion = 4.0.0-alpha-1
>
> On Thu, Oct 20, 2022 at 6:53 AM Ayush Saxena  wrote:
>
> > Hi Denys,
> > Flaging the version stuff here what we discussed offline.
> >
> > The version 4.0.0 was used prior the decision to rename it 4.0.0-alpha1
> > was taken, but the rename was not done on the Jira.
> >
> > It still shows around 3K tickets resolved on version 4.0.0, which got
> > released already as part of the last 4.0.0-alpha1 release[1]
> >
> > We should rename it in the Jira to avoid issues with building Release
> > Notes for our next 4.0.0 release
> >
> > A simple INFRA ticket or anyone with Hive Jira Admin rights should be
> able
> > to do so.
> >
> > [1]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%204.0.0
> >
> > -Ayush
> >
> >
> > > On 19-Oct-2022, at 9:09 PM, Denys Kuzmenko  .invalid>
> > wrote:
> > >
> > > Hi Team,
> > >
> > > Branching for Hive *4.0.0-alpha-2* was done today:
> > > https://github.com/apache/hive/tree/branch-4.0.0-alpha-2
> > >
> > > The next development version is *4.0.0-SNAPSHOT*
> > >
> > > *alpha-2 *branch would be open for commits until Monday. If you would
> > like
> > > to include something major in it, but need more time, please let me
> know.
> > >
> > > Best regards,
> > > Denys
> >
>


[Branching] Apache Hive 4.0.0-alpha-2 Release

2022-10-19 Thread Denys Kuzmenko
Hi Team,

Branching for Hive *4.0.0-alpha-2* was done today:
https://github.com/apache/hive/tree/branch-4.0.0-alpha-2

The next development version is *4.0.0-SNAPSHOT*

*alpha-2 *branch would be open for commits until Monday. If you would like
to include something major in it, but need more time, please let me know.

Best regards,
Denys


[jira] [Created] (HIVE-26645) Preparing for 4.0.0-GA development

2022-10-18 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26645:
-

 Summary: Preparing for 4.0.0-GA development
 Key: HIVE-26645
 URL: https://issues.apache.org/jira/browse/HIVE-26645
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-26487) Auto-compaction may hang or skip some of the eligible items

2022-08-19 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26487:
-

 Summary: Auto-compaction may hang or skip some of the eligible 
items 
 Key: HIVE-26487
 URL: https://issues.apache.org/jira/browse/HIVE-26487
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-26433) HivePrivilegeObject's objectName is NULL when JdbcStorageHandler is used with METASTORE type

2022-07-27 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26433:
-

 Summary: HivePrivilegeObject's objectName is NULL when 
JdbcStorageHandler is used with METASTORE type
 Key: HIVE-26433
 URL: https://issues.apache.org/jira/browse/HIVE-26433
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-26416) AcidUtils$MetaDataFile.isRawFormatFile() throws InvalidProtocolBufferException for non-ORC file

2022-07-20 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26416:
-

 Summary: AcidUtils$MetaDataFile.isRawFormatFile() throws 
InvalidProtocolBufferException for non-ORC file
 Key: HIVE-26416
 URL: https://issues.apache.org/jira/browse/HIVE-26416
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


{code}
Caused by: com.google.protobuf.InvalidProtocolBufferException: Protocol message 
tag had invalid wire type.
at 
com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:99)
at 
com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:498)
at 
com.google.protobuf.GeneratedMessage.parseUnknownField(GeneratedMessage.java:193)
at org.apache.orc.OrcProto$PostScript.(OrcProto.java:18763)
at org.apache.orc.OrcProto$PostScript.(OrcProto.java:18721)
at 
org.apache.orc.OrcProto$PostScript$1.parsePartialFrom(OrcProto.java:18859)
at 
org.apache.orc.OrcProto$PostScript$1.parsePartialFrom(OrcProto.java:18854)
at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:89)
at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:95)
at com.google.protobuf.AbstractParser.parseFrom(AbstractParser.java:49)
at org.apache.orc.OrcProto$PostScript.parseFrom(OrcProto.java:19253)
at org.apache.orc.impl.ReaderImpl.extractPostScript(ReaderImpl.java:454)
at org.apache.orc.impl.ReaderImpl.extractFileTail(ReaderImpl.java:582)
at org.apache.orc.impl.ReaderImpl.(ReaderImpl.java:369)
at 
org.apache.hadoop.hive.ql.io.orc.ReaderImpl.(ReaderImpl.java:61)
at 
org.apache.hadoop.hive.ql.io.orc.OrcFile.createReader(OrcFile.java:112)
at 
org.apache.hadoop.hive.ql.io.AcidUtils$MetaDataFile.isRawFormatFile(AcidUtils.java:2585)
{code}



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


[jira] [Created] (HIVE-26293) Migrate remaining exclusive DDL operations to EXCL_WRITE lock & bug fixes

2022-06-06 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26293:
-

 Summary: Migrate remaining exclusive DDL operations to EXCL_WRITE 
lock & bug fixes
 Key: HIVE-26293
 URL: https://issues.apache.org/jira/browse/HIVE-26293
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (HIVE-26252) Missing locks in case of MERGE with multiple branches

2022-05-20 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26252:
-

 Summary: Missing locks in case of MERGE with multiple branches
 Key: HIVE-26252
 URL: https://issues.apache.org/jira/browse/HIVE-26252
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (HIVE-26165) Remove READ locks for ACID tables with SoftDelete enabled

2022-04-22 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26165:
-

 Summary: Remove READ locks for ACID tables with SoftDelete enabled
 Key: HIVE-26165
 URL: https://issues.apache.org/jira/browse/HIVE-26165
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Created] (HIVE-26149) Non blocking DROP DATABASE implementation

2022-04-18 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26149:
-

 Summary: Non blocking DROP DATABASE implementation
 Key: HIVE-26149
 URL: https://issues.apache.org/jira/browse/HIVE-26149
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26129) Non blocking DROP CONNECTOR

2022-04-11 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26129:
-

 Summary: Non blocking DROP CONNECTOR
 Key: HIVE-26129
 URL: https://issues.apache.org/jira/browse/HIVE-26129
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


Use a less restrictive lock for data connectors, they do not have any 
dependencies on other tables. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26121) Hive transaction rollback should be thread-safe

2022-04-06 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26121:
-

 Summary: Hive transaction rollback should be thread-safe
 Key: HIVE-26121
 URL: https://issues.apache.org/jira/browse/HIVE-26121
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26106) Non blocking ADD, DROP CONSTRAINT

2022-04-01 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26106:
-

 Summary: Non blocking ADD, DROP CONSTRAINT
 Key: HIVE-26106
 URL: https://issues.apache.org/jira/browse/HIVE-26106
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


Re: [VOTE] Apache Hive 4.0.0-alpha-1 Release Candidate 2

2022-03-28 Thread Denys Kuzmenko
+1

* Downloaded the release candidate artifacts and verified the signatures
and checksums;
* Built from the release sources;
* Initialized schema using schematool and launched hiveserver2 locally;
* Used beeline to connect:
- Created a few tables and loaded data into them.
- Executed some simple queries.

Best regards,
Denys

On Sat, Mar 26, 2022 at 11:24 PM Stamatis Zampetakis 
wrote:

> Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
>
>  * Checked signatures and checksums OK
>  * Checked diff between repo and release sources (diff -qr hive
> apache-hive-4.0.0-alpha-1-src) OK
>  * Built from git tag (mvn clean install -DskipTests -Pitests) OK
>  * Built from release sources (mvn clean install -DskipTests -Pitests) OK
>  * Run smoke tests on pseudo cluster using hive-dev-box OK
>
> All of the issues that were found in the previous RC are either resolved or
> tracked under respective JIRAs to be solved for the next release.
>
> Smoke tests included:
> * Derby metastore initialization
> * simple CREATE TABLE statements;
> * basic INSERT INTO VALUES statements;
> * basic SELECT * FROM WHERE variations;
> * EXPLAIN statement variations;
> * ANALYZE TABLE variations;
>
> +1 (non-binding)
>
> Best,
> Stamatis
>
> On Thu, Mar 24, 2022 at 12:01 PM Peter Vary 
> wrote:
>
> > Hi Team,
> >
> > Apache Hive 4.0.0-alpha-1 Release Candidate 2 is available here:
> > https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc2/ <
> > https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc2/>
> >
> > The checksums are these:
> > - 1e450197dbf847696b05042eb68b78b968064f1f1b369a7fb0b77a6329a27809
> > apache-hive-4.0.0-alpha-1-bin.tar.gz
> > - a21a609ec2e30f8cc656242c545bb3a04de21c2a1eee90808648e3aa4bf3d04e
> > apache-hive-4.0.0-alpha-1-src.tar.gz
> >
> > Maven artifacts are available here:
> > https://repository.apache.org/content/repositories/orgapachehive-1113/ <
> > https://repository.apache.org/content/repositories/orgapachehive-1113/>
> >
> > The tag 4.0.0-alpha-1-rc1 has been applied to the source for this release
> > in github, you can see it at
> > https://github.com/apache/hive/tree/release-4.0.0-alpha-1-rc1 <
> > https://github.com/apache/hive/tree/release-4.0.0-alpha-1-rc1>
> >
> > The git commit hash is:
> >
> >
> https://github.com/apache/hive/commit/357d4906f5c806d585fd84db57cf296e12e6049b
> > <
> >
> https://github.com/apache/hive/commit/357d4906f5c806d585fd84db57cf296e12e6049b
> > >
> >
> > Voting will conclude in 72 hours.
> >
> > All interested parties: Please test.
> > Hive PMC Members: Please test and vote.
> >
> > Thanks.
>


[jira] [Created] (HIVE-26076) Non blocking ADD PARTITION if not exists

2022-03-25 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26076:
-

 Summary: Non blocking ADD PARTITION if not exists
 Key: HIVE-26076
 URL: https://issues.apache.org/jira/browse/HIVE-26076
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26053) Non blocking DROP VIEW

2022-03-21 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26053:
-

 Summary: Non blocking DROP VIEW
 Key: HIVE-26053
 URL: https://issues.apache.org/jira/browse/HIVE-26053
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26052) Non-blocking DROP MATERIALIZED VIEW implementation

2022-03-21 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26052:
-

 Summary: Non-blocking DROP MATERIALIZED VIEW implementation
 Key: HIVE-26052
 URL: https://issues.apache.org/jira/browse/HIVE-26052
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26051) Non blocking Alter Materialized View Rewrite

2022-03-21 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26051:
-

 Summary: Non blocking Alter Materialized View Rewrite
 Key: HIVE-26051
 URL: https://issues.apache.org/jira/browse/HIVE-26051
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-26023) Non blocking REPLACE, RENAME COLUMNS implementation

2022-03-09 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-26023:
-

 Summary: Non blocking REPLACE, RENAME COLUMNS implementation
 Key: HIVE-26023
 URL: https://issues.apache.org/jira/browse/HIVE-26023
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25956) Non blocking RENAME TABLE implementation

2022-02-14 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25956:
-

 Summary: Non blocking RENAME TABLE implementation
 Key: HIVE-25956
 URL: https://issues.apache.org/jira/browse/HIVE-25956
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


Re: [EXTERNAL] Re: [ANNOUNCE] New committer: Ayush Saxena

2022-02-08 Thread Denys Kuzmenko
Congrats Ayush!

On Tue, Feb 8, 2022 at 5:51 AM Sankar Hariappan
 wrote:

> Congrats Ayush!
>
> --
> Sankar
>
> -Original Message-
> From: László Bodor 
> Sent: 07 February 2022 21:20
> To: dev@hive.apache.org
> Subject: [EXTERNAL] Re: [ANNOUNCE] New committer: Ayush Saxena
>
> Welcome Ayush, well deserved!
>
> Ashutosh Chauhan  ezt írta (időpont: 2022. febr.
> 7., H, 16:35):
>
> > Hi all,
> > Apache Hive's Project Management Committee (PMC) has invited Ayush to
> > become a committer, and we are pleased to announce that he has accepted!
> >
> > Ayush welcome, thank you for your contributions, and we look forward
> > to your further interactions with the community!
> > Ashutosh (on behalf of Hive PMC)
> >
>


Re: [EXTERNAL] [ANNOUNCE] Denys Kuzmenko joins Hive PMC

2022-02-08 Thread Denys Kuzmenko
Thank you! I am truly honored.

On Tue, Feb 8, 2022 at 5:51 AM Sankar Hariappan
 wrote:

> Congrats Denys!
>
> --
> Sankar
>
> -Original Message-
> From: Ashutosh Chauhan 
> Sent: 07 February 2022 22:10
> To: dev@hive.apache.org
> Subject: [EXTERNAL] [ANNOUNCE] Denys Kuzmenko joins Hive PMC
>
> 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)
>


[jira] [Created] (HIVE-25934) Non blocking RENAME PARTITION implementation

2022-02-07 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25934:
-

 Summary: Non blocking RENAME PARTITION implementation
 Key: HIVE-25934
 URL: https://issues.apache.org/jira/browse/HIVE-25934
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25904) ObjectStore's updateTableColumnStatistics is not ThreadSafe

2022-01-27 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25904:
-

 Summary: ObjectStore's updateTableColumnStatistics is not 
ThreadSafe
 Key: HIVE-25904
 URL: https://issues.apache.org/jira/browse/HIVE-25904
 Project: Hive
  Issue Type: Bug
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25881) isEligibleForCompaction runs under the ForkJoinPool.commonPool

2022-01-19 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25881:
-

 Summary: isEligibleForCompaction runs under the 
ForkJoinPool.commonPool
 Key: HIVE-25881
 URL: https://issues.apache.org/jira/browse/HIVE-25881
 Project: Hive
  Issue Type: Bug
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25781) Restore multi-threaded support in Cleaner

2021-12-07 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25781:
-

 Summary: Restore multi-threaded support in Cleaner
 Key: HIVE-25781
 URL: https://issues.apache.org/jira/browse/HIVE-25781
 Project: Hive
  Issue Type: Sub-task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25755) TestTxnCommands classes refactor

2021-12-01 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25755:
-

 Summary: TestTxnCommands classes refactor
 Key: HIVE-25755
 URL: https://issues.apache.org/jira/browse/HIVE-25755
 Project: Hive
  Issue Type: Test
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25710) Config used to enable non-blocking TRUNCATE is not properly propagated

2021-11-16 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25710:
-

 Summary: Config used to enable non-blocking TRUNCATE is not 
properly propagated
 Key: HIVE-25710
 URL: https://issues.apache.org/jira/browse/HIVE-25710
 Project: Hive
  Issue Type: Sub-task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25688) Non blocking DROP PARTITION implementation

2021-11-11 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25688:
-

 Summary: Non blocking DROP PARTITION implementation
 Key: HIVE-25688
 URL: https://issues.apache.org/jira/browse/HIVE-25688
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (HIVE-25645) Query-based compaction doesn't work when partition column type is boolean

2021-10-25 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25645:
-

 Summary: Query-based compaction doesn't work when partition column 
type is boolean
 Key: HIVE-25645
 URL: https://issues.apache.org/jira/browse/HIVE-25645
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25631) Initiator speed-up: only read compaction history once per loop

2021-10-21 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25631:
-

 Summary: Initiator speed-up: only read compaction history once per 
loop
 Key: HIVE-25631
 URL: https://issues.apache.org/jira/browse/HIVE-25631
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25623) Create a parametrized test to check against the disabled MIN_HISTORY config

2021-10-19 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25623:
-

 Summary: Create a parametrized test to check against the disabled 
MIN_HISTORY config
 Key: HIVE-25623
 URL: https://issues.apache.org/jira/browse/HIVE-25623
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25603) Restore original method signature in VectorizedOrcAcidRowBatchReader.getDeleteDeltaDirsFromSplit

2021-10-08 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25603:
-

 Summary: Restore original method signature in 
VectorizedOrcAcidRowBatchReader.getDeleteDeltaDirsFromSplit
 Key: HIVE-25603
 URL: https://issues.apache.org/jira/browse/HIVE-25603
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25516) ITestDbTxnManager is broken after HIVE-24120

2021-09-13 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25516:
-

 Summary: ITestDbTxnManager is broken after HIVE-24120
 Key: HIVE-25516
 URL: https://issues.apache.org/jira/browse/HIVE-25516
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25503) Add cleanup for the duplicate COMPLETED_TXN_COMPONENTS entries

2021-09-06 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25503:
-

 Summary: Add cleanup for the duplicate COMPLETED_TXN_COMPONENTS 
entries
 Key: HIVE-25503
 URL: https://issues.apache.org/jira/browse/HIVE-25503
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


Performace improvement. Accumulated entries in COMPLETED_TXN_COMPONENTS can 
lead to query performance degradation.



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


[jira] [Created] (HIVE-25502) Cleaner causes data loss when processing aborted txn with DP

2021-09-06 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25502:
-

 Summary: Cleaner causes data loss when processing aborted txn with 
DP 
 Key: HIVE-25502
 URL: https://issues.apache.org/jira/browse/HIVE-25502
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25441) Incorrect deltas split for sub-compactions when using `hive.compactor.max.num.delta`

2021-08-10 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25441:
-

 Summary: Incorrect deltas split for sub-compactions when using 
`hive.compactor.max.num.delta`
 Key: HIVE-25441
 URL: https://issues.apache.org/jira/browse/HIVE-25441
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25393) Prevent concurrent compaction and DDL operations

2021-07-27 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25393:
-

 Summary: Prevent concurrent compaction and DDL operations
 Key: HIVE-25393
 URL: https://issues.apache.org/jira/browse/HIVE-25393
 Project: Hive
  Issue Type: Task
Reporter: Denys Kuzmenko


Introduce read locks in compaction (MR, Minor Query-based) that would prevent 
concurrency issues with DDL operations (DROP/RENAME table).



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


[jira] [Created] (HIVE-25259) Tweak delta metrics with custom MBean for Prometheus

2021-06-16 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25259:
-

 Summary: Tweak delta metrics with custom MBean for Prometheus
 Key: HIVE-25259
 URL: https://issues.apache.org/jira/browse/HIVE-25259
 Project: Hive
  Issue Type: Sub-task
Reporter: Denys Kuzmenko






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


[jira] [Created] (HIVE-25217) Move isEligibleForCompaction evaluation under the Initiator thread pool

2021-06-08 Thread Denys Kuzmenko (Jira)
Denys Kuzmenko created HIVE-25217:
-

 Summary: Move isEligibleForCompaction evaluation under the 
Initiator thread pool
 Key: HIVE-25217
 URL: https://issues.apache.org/jira/browse/HIVE-25217
 Project: Hive
  Issue Type: Bug
Reporter: Denys Kuzmenko


Checking for eligibility >1 mil of distinct table / partition combinations can 
take a while by the Initiator since all steps are performed in the main thread. 



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


  1   2   3   4   >