Re: Fw: apache/hive security vulnerabilities.

[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.

[Simhadri G]

Hi guys,

I checked for jackson-databind-2.4.0. It seems to be a transitive
dependency from htrace-core .

[image: image.png]


On Wed, Jun 19, 2024 at 8:29 PM Stamatis Zampetakis 
wrote:

> I am pretty sure that the old Jackson versions are shaded somewhere
> inside the jars of Hive dependencies. We probably need to inspect the
> contents of our binary distribution of Hive 4.0.0 and take corrective
> actions if needed.
>
> Best,
> Stamatis
>
> On Wed, Jun 19, 2024 at 4:35 PM Denys Kuzmenko 
> wrote:
> >
> > 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.

[Stamatis Zampetakis]

I am pretty sure that the old Jackson versions are shaded somewhere
inside the jars of Hive dependencies. We probably need to inspect the
contents of our binary distribution of Hive 4.0.0 and take corrective
actions if needed.

Best,
Stamatis

On Wed, Jun 19, 2024 at 4:35 PM Denys Kuzmenko  wrote:
>
> 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.

[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.

[Iyer, Sreekanth]

Hi Denys

That's right. jackson-databind version 2.16.1 does not have any CVEs. I also 
saw that there was HIVE ticket to update to this version. [HIVE-28073] Upgrade 
jackson version to 2.16.1 - ASF JIRA 
(apache.org) . The ticket 
also mentions this was fixed in Hive 4.0.0.

But the docker image, that I downloaded from dockerhub - apache/hive Tags | 
Docker Hub shows that there are two 
old versions of the package in use within the image. (2.4.0 and 2.9.4)

[cid:4312c910-a81a-48cb-ab63-556c3541d39e]



Thanks
Regards
Sreek


From: Denys Kuzmenko 
Sent: Wednesday, June 19, 2024 6:06 PM
To: dev@hive.apache.org 
Subject: Re: apache/hive security vulnerabilities.

Caution: This is an external email. Verify any links or attachments before 
opening.


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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmvnrepository.com%2Fartifact%2Fcom.fasterxml.jackson.core%2Fjackson-databind%2F2.16.1=05%7C02%7CSreekanth.Iyer%40verint.com%7C16e6ff111de249dc900408dc905c9ecf%7Cbb2ed304409949cfb081cbb7a3a580ca%7C0%7C0%7C638543974683935188%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=B8vz0jyrFgtlzJ81yq4QbMz29Kkovl%2BFh%2BS0blplAOk%3D=0


com.fasterxml.jackson
jackson-bom
2.16.1
pom
import




This electronic message may contain proprietary and confidential information of 
Verint Systems Inc., its affiliates and/or subsidiaries. The information is 
intended to be for the use of the individual(s) or entity(ies) named above. If 
you are not the intended recipient (or authorized to receive this e-mail for 
the intended recipient), you may not use, copy, disclose or distribute to 
anyone this message or any information contained in this message. If you have 
received this electronic message in error, please notify us by replying to this 
e-mail.

Re: apache/hive security vulnerabilities.

[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

[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 

Fwd: about hive4.0.0 error

[张三]

-- 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 [00b77a5e-7cec-4e10-a0ae-f94450a56ab0
HiveServer2-Handler-Pool: Thread-54] operation.OperationManager: Adding
opera
tion: OperationHandle [opType=EXECUTE_STATEMENT,
getHandleIdentifier()=9c5817e6-131a-4e60-bfe3-faa066a61119] SessionHandle
[00b77a5e-7cec-4e10-a0ae-f94450a56ab0]2024-06-19T11:27:48,654  INFO
[00b77a5e-7cec-4e10-a0ae-f94450a56ab0 HiveServer2-Handler-Pool: Thread-54]
common.LogUtils: Thread context registra
tion is done.2024-06-19T11:27:48,654  INFO

Re: Hive 4.0 interview/podcast

[Stamatis Zampetakis]

The community worked really hard to get the 4.0.0 release into a great
shape and me along with everyone else who contributed to the project is
very happy to see its adoption by the users. Thanks Rich for giving Hive
the opportunity to feature on FeatherCast and help reach a wider audience!

Kudos to the entire community for shaping this huge release with ~5K
commits and ~400 code contributors [1]!!!

Best,
Stamatis

[1] git log --format=%an rel/release-3.0.0..rel/release-4.0.0 | sort -u |
wc -l

On Tue, Jun 11, 2024 at 4:38 PM Simhadri G  wrote:

> Great interview!!
>
> Thanks Rich and Stamatis for the podcast!!
>
> On Tue, Jun 11, 2024 at 7:46 PM Butao Zhang  wrote:
>
>> It is a really valuable interview!!!
>> Thanks Rich and Stamatis!!!
>>
>>
>>
>> Thanks,
>> Butao Zhang
>>  Replied Message 
>> From Ayush Saxena 
>> Date 6/11/2024 21:57
>> To ,
>>  
>> Subject Re: Hive 4.0 interview/podcast
>> Hey Guys,
>> I just watched the interview - It's awesome. Big thanx to Rich &
>> Stamatis for putting this together!!!
>>
>> -Ayush
>>
>> On Tue, 11 Jun 2024 at 18:38, Rich Bowen  wrote:
>>
>>
>> Hi, folks. Congratulations on the release of Hive 4.0. I've just
>> published an interview with Stamatis Zampetakis, and it's live at
>> https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k
>> (just the audio).
>>
>> Thanks, Stamatis! It was good talking with you.
>>
>> --Rich
>>
>>

Re: Hive 4.0 interview/podcast

[Simhadri G]

Great interview!!

Thanks Rich and Stamatis for the podcast!!

On Tue, Jun 11, 2024 at 7:46 PM Butao Zhang  wrote:

> It is a really valuable interview!!!
> Thanks Rich and Stamatis!!!
>
>
>
> Thanks,
> Butao Zhang
>  Replied Message 
> From Ayush Saxena 
> Date 6/11/2024 21:57
> To ,
>  
> Subject Re: Hive 4.0 interview/podcast
> Hey Guys,
> I just watched the interview - It's awesome. Big thanx to Rich &
> Stamatis for putting this together!!!
>
> -Ayush
>
> On Tue, 11 Jun 2024 at 18:38, Rich Bowen  wrote:
>
>
> Hi, folks. Congratulations on the release of Hive 4.0. I've just published
> an interview with Stamatis Zampetakis, and it's live at
> https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k
> (just the audio).
>
> Thanks, Stamatis! It was good talking with you.
>
> --Rich
>
>

Re: Hive 4.0 interview/podcast

[Butao Zhang]

It is a really valuable interview!!!
Thanks Rich and Stamatis!!!






Thanks,
Butao Zhang
 Replied Message 
| From | Ayush Saxena |
| Date | 6/11/2024 21:57 |
| To | ,
 |
| Subject | Re: Hive 4.0 interview/podcast |
Hey Guys,
I just watched the interview - It's awesome. Big thanx to Rich &
Stamatis for putting this together!!!

-Ayush

On Tue, 11 Jun 2024 at 18:38, Rich Bowen  wrote:

Hi, folks. Congratulations on the release of Hive 4.0. I've just published an 
interview with Stamatis Zampetakis, and it's live at 
https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k (just the 
audio).

Thanks, Stamatis! It was good talking with you.

--Rich

Re: Hive 4.0 interview/podcast

[Ayush Saxena]

Hey Guys,
I just watched the interview - It's awesome. Big thanx to Rich &
Stamatis for putting this together!!!

-Ayush

On Tue, 11 Jun 2024 at 18:38, Rich Bowen  wrote:
>
> Hi, folks. Congratulations on the release of Hive 4.0. I've just published an 
> interview with Stamatis Zampetakis, and it's live at 
> https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k (just 
> the audio).
>
> Thanks, Stamatis! It was good talking with you.
>
> --Rich

Hive 4.0 interview/podcast

[Rich Bowen]

Hi, folks. Congratulations on the release of Hive 4.0. I've just published an 
interview with Stamatis Zampetakis, and it's live at 
https://youtu.be/7HX2MieyzW4 (video) and at https://wp.me/p8gHED-41k (just the 
audio).

Thanks, Stamatis! It was good talking with you.

--Rich

Re: Inquiry About Release Date for Hive-exec-core: 4.0.1

[Ayush Saxena]

Should be there in 4.0.1 release, expected in about 2 months-AyushOn 29 May 2024, at 4:29 PM, Mergu Ravi  wrote:Sorry, I mentioned the wrong version; the version is 4.1.0.On Wed, May 29, 2024 at 4:27 PM Mergu Ravi  wrote:Hi Hive Team,I hope this message finds you well.I am writing to inquire about the release date for Hive-exec-core 4.0.1. Specifically, I am interested in the timeline for the release of the fix detailed in the Jira story HIVE-28211.Could you please provide an update on when we can expect this release to be available?Thank you for your assistance.--Thanks & Regards,Ravi MerguSMTS-2o:  +91 40 64535355m: +91 9959618687w: 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
-- Thanks & Regards,Ravi MerguSMTS-2o:  +91 40 64535355m: +91 9959618687w: 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: [Discussion] HIVE-28211: Restore hive-exec:core jar

[Mergu Ravi]

When is the hive-exec-core:4.1.0 expected to be released?
HIVE-28211 

On Fri, May 3, 2024 at 3:43 PM Denys Kuzmenko  wrote:

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


-- 

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: Inquiry About Release Date for Hive-exec-core: 4.0.1

[Mergu Ravi]

Sorry, I mentioned the wrong version; the version is 4.1.0.

On Wed, May 29, 2024 at 4:27 PM Mergu Ravi 
wrote:

> Hi Hive Team,
>
> I hope this message finds you well.
>
> I am writing to inquire about the release date for Hive-exec-core 4.0.1.
> Specifically, I am interested in the timeline for the release of the fix
> detailed in the Jira story HIVE-28211
> .
>
> Could you please provide an update on when we can expect this release to
> be available?
>
> Thank you for your assistance.
> --
>
> 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
>
>

-- 

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

Inquiry About Release Date for Hive-exec-core: 4.0.1

[Mergu Ravi]

Hi Hive Team,

I hope this message finds you well.

I am writing to inquire about the release date for Hive-exec-core 4.0.1.
Specifically, I am interested in the timeline for the release of the fix
detailed in the Jira story HIVE-28211
.

Could you please provide an update on when we can expect this release to be
available?

Thank you for your assistance.
--

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: Cluster for Performance Testing Hive

[Stamatis Zampetakis]

Hive is open source so there are millions of ways to help even without
being under the sponsorship flag.

Quick examples:
"Hey, I have set up this machine there and I can give you access to
run benchmarks"
"In my company X we are using Hive and we decided to run nightly
benchmarks on our inhouse clusters; the results are publicly available
and you can access them here."

In a nutshell we are open to any kind of help that someone is willing to offer.

The official website of Hive [1] has all the necessary links about
donations, sponsorships, etc., under the ASF dropdown menu.

Best,
Stamatis

[1] https://hive.apache.org/


On Wed, May 22, 2024 at 10:38 AM Eugene Ryan  wrote:
>
> Thanks for that, Stamatis. Plenty of food for thought there. What would you 
> think of the best way of getting sponsors on board - when they 
> read/contribute here, for example?
>
> From the list of requirements to start a VM, the following could be used as 
> part of the process, I imagine:
> Maintainers:
> "Provide the name, Apache ID, and contact info for at least three PMC 
> members who will maintain the vm " - read “maintain cluster” here or perhaps 
> this would be the sponsor
>
> On Tue, May 21, 2024 at 1:36 PM Stamatis Zampetakis  wrote:
>>
>> Hey Eugene,
>>
>> Having a cluster for performance testing is a great idea and it is
>> something that has popped up in various contexts.
>>
>> The most common way to obtain such clusters is via sponsors (companies
>> or individuals) donating resources to the project. For example, the
>> Hive CI is now running mostly on resources donated by Cloudera.
>>
>> There seems to be a process about requesting resources from the Apache
>> Infra team [1] but I am not aware of other ASF projects following this
>> path for performance testing. Most likely the easiest and fastest way
>> to move this forward is through a sponsor. Depending on where the
>> resources come from will also determine the design, implementation,
>> and maintenance.
>>
>> Best,
>> Stamatis
>>
>> [1] https://infra.apache.org/vm-for-project.html
>>
>> On Tue, May 21, 2024 at 11:25 AM Eugene Ryan  wrote:
>> >
>> > Hi,
>> >
>> > I'd like to get folks' opinions on having a public cluster for performance
>> > testing Hive code and getting an early read on whether a commit / build has
>> > caused a performance degradation over existing code.
>> >
>> > There are already well known workloads available, for example, TPC-DS 
>> > (https://github.com/hortonworks/hive-testbench) that can be run so I'm not 
>> > talking about performance test code itself (although that should be as 
>> > easy as possible on top of a dedicated cluster).
>> >
>> > The benefits to the community would be:
>> >- A dedicated environment, not necessarily leaving it to the vendors to 
>> > integrate open-source later into their stacks and only find out some time 
>> > later about performance problems
>> >- Something that can be left set up & running -  no setup and tear-down
>> >process needed every time a performance run is required
>> >- An automated process for performance testing - no manual setup or
>> >intervention
>> >
>> > Concerns:
>> >- Budget
>> >- Who administers the cluster, ie.. who sets it up, fixes it when down
>> >
>> > I'd like to get some opinions on what the process for getting this to
>> > happen would be, bearing in mind that certain things may well be obstacles 
>> > (budget) that have to be solved upfront before anything else happens:
>> >-Budget approval
>> >-   Approval / Sign off - how & who?
>> >-Architecture / pipeline design
>> >-   Implementation
>> >
>> > Thanks, all opinions welcome.
>> > Eugene
>> >
>
>
>
> --
> Eugene

Re: Cluster for Performance Testing Hive

[Eugene Ryan]

Thanks for that, Stamatis. Plenty of food for thought there. What would you
think of the best way of getting sponsors on board - when they
read/contribute here, for example?

>From the list of requirements to start a VM, the following could be used as
part of the process, I imagine:
Maintainers:
"Provide the name, Apache ID, and contact info for at least three PMC
members who will maintain the vm " - read “maintain cluster” here or
perhaps this would be the sponsor

On Tue, May 21, 2024 at 1:36 PM Stamatis Zampetakis 
wrote:

> Hey Eugene,
>
> Having a cluster for performance testing is a great idea and it is
> something that has popped up in various contexts.
>
> The most common way to obtain such clusters is via sponsors (companies
> or individuals) donating resources to the project. For example, the
> Hive CI is now running mostly on resources donated by Cloudera.
>
> There seems to be a process about requesting resources from the Apache
> Infra team [1] but I am not aware of other ASF projects following this
> path for performance testing. Most likely the easiest and fastest way
> to move this forward is through a sponsor. Depending on where the
> resources come from will also determine the design, implementation,
> and maintenance.
>
> Best,
> Stamatis
>
> [1] https://infra.apache.org/vm-for-project.html
>
> On Tue, May 21, 2024 at 11:25 AM Eugene Ryan 
> wrote:
> >
> > Hi,
> >
> > I'd like to get folks' opinions on having a public cluster for
> performance
> > testing Hive code and getting an early read on whether a commit / build
> has
> > caused a performance degradation over existing code.
> >
> > There are already well known workloads available, for example, TPC-DS (
> https://github.com/hortonworks/hive-testbench) that can be run so I'm not
> talking about performance test code itself (although that should be as easy
> as possible on top of a dedicated cluster).
> >
> > The benefits to the community would be:
> >- A dedicated environment, not necessarily leaving it to the vendors
> to integrate open-source later into their stacks and only find out some
> time later about performance problems
> >- Something that can be left set up & running -  no setup and
> tear-down
> >process needed every time a performance run is required
> >- An automated process for performance testing - no manual setup or
> >intervention
> >
> > Concerns:
> >- Budget
> >- Who administers the cluster, ie.. who sets it up, fixes it when down
> >
> > I'd like to get some opinions on what the process for getting this to
> > happen would be, bearing in mind that certain things may well be
> obstacles (budget) that have to be solved upfront before anything else
> happens:
> >-Budget approval
> >-   Approval / Sign off - how & who?
> >-Architecture / pipeline design
> >-   Implementation
> >
> > Thanks, all opinions welcome.
> > Eugene
> >
>


-- 
Eugene

Re: Cluster for Performance Testing Hive

[Stamatis Zampetakis]

Hey Eugene,

Having a cluster for performance testing is a great idea and it is
something that has popped up in various contexts.

The most common way to obtain such clusters is via sponsors (companies
or individuals) donating resources to the project. For example, the
Hive CI is now running mostly on resources donated by Cloudera.

There seems to be a process about requesting resources from the Apache
Infra team [1] but I am not aware of other ASF projects following this
path for performance testing. Most likely the easiest and fastest way
to move this forward is through a sponsor. Depending on where the
resources come from will also determine the design, implementation,
and maintenance.

Best,
Stamatis

[1] https://infra.apache.org/vm-for-project.html

On Tue, May 21, 2024 at 11:25 AM Eugene Ryan  wrote:
>
> Hi,
>
> I'd like to get folks' opinions on having a public cluster for performance
> testing Hive code and getting an early read on whether a commit / build has
> caused a performance degradation over existing code.
>
> There are already well known workloads available, for example, TPC-DS 
> (https://github.com/hortonworks/hive-testbench) that can be run so I'm not 
> talking about performance test code itself (although that should be as easy 
> as possible on top of a dedicated cluster).
>
> The benefits to the community would be:
>- A dedicated environment, not necessarily leaving it to the vendors to 
> integrate open-source later into their stacks and only find out some time 
> later about performance problems
>- Something that can be left set up & running -  no setup and tear-down
>process needed every time a performance run is required
>- An automated process for performance testing - no manual setup or
>intervention
>
> Concerns:
>- Budget
>- Who administers the cluster, ie.. who sets it up, fixes it when down
>
> I'd like to get some opinions on what the process for getting this to
> happen would be, bearing in mind that certain things may well be obstacles 
> (budget) that have to be solved upfront before anything else happens:
>-Budget approval
>-   Approval / Sign off - how & who?
>-Architecture / pipeline design
>-   Implementation
>
> Thanks, all opinions welcome.
> Eugene
>

Cluster for Performance Testing Hive

[Eugene Ryan]

Hi,

I'd like to get folks' opinions on having a public cluster for performance
testing Hive code and getting an early read on whether a commit / build has
caused a performance degradation over existing code.

There are already well known workloads available, for example, TPC-DS (
https://github.com/hortonworks/hive-testbench) that can be run so I'm not
talking about performance test code itself (although that should be as
easy as possible on top of a dedicated cluster).

The benefits to the community would be:
   - A dedicated environment, not necessarily leaving it to the vendors
to integrate open-source later into their stacks and only find out some
time later about performance problems
   - Something that can be left set up & running -  no setup and tear-down
   process needed every time a performance run is required
   - An automated process for performance testing - no manual setup or
   intervention

Concerns:
   - Budget
   - Who administers the cluster, ie.. who sets it up, fixes it when down

I'd like to get some opinions on what the process for getting this to
happen would be, bearing in mind that certain things may well be obstacles
(budget) that have to be solved upfront before anything else happens:
   -Budget approval
   -   Approval / Sign off - how & who?
   -Architecture / pipeline design
   -   Implementation

Thanks, all opinions welcome.
Eugene

[ANNOUNCE] Hive 2.x EOL

[Ayush Saxena]

Hi All,
The Apache Hive Community has voted to declare the 2.x release line as End of 
Life. This means no further updates or releases will be made for this release 
line.

We urge all Hive 2.x users to upgrade to the latest versions promptly to 
benefit from new features and ongoing support.

-Ayush Saxena
(On Behalf of Apache Hive PMC)

[VOTE][RESULT] Mark Hive 2.x EOL

[Ayush Saxena]

Thanx Everyone for the participation, We have 15 +1s (5 Binding) in
favour with no -1s casted:

* Naveen Gangam(Binding)
* Zoltan Ratkai
* Sourabh Badhya
* Krisztian Kasa(Binding)
* Okumin
* Aman Sinha
* Mahesh Raju Somaraju
* Chao Sun(Binding)
* Kokila Narayanan
* Simhadri G
* Stamatis Zampetakis(Binding)
* Denys Kuzmenko
* Attila Turoczy
* Butao Zhang
* Ayush Saxena(Binding)

The vote passes, I will make the announcements and take care of other
requirements.

-Ayush

On Wed, 15 May 2024 at 20:31, Naveen Gangam
 wrote:
>
> +1 Totally
>
> On Tue, May 14, 2024 at 3:30 AM Zoltán Rátkai  
> wrote:
>>
>> +1 (non-binding)
>>
>> Regards,
>>
>> Zoltan Ratkai
>>
>> On Tue, May 14, 2024 at 5:42 AM Sourabh Badhya 
>>  wrote:
>>>
>>> +1 (non-binding)
>>>
>>> Regards,
>>> Sourabh Badhya
>>>
>>> On Mon, May 13, 2024 at 10:31 PM Krisztian Kasa 
>>>  wrote:

 +1 (binding)

 On Mon, May 13, 2024 at 4:55 PM Okumin  wrote:
>
> +1 (non-binding)
>
> I appreciate the community's efforts in maintaining 2.x for so long.
>
> Thanks,
> Okumin
>
> On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta  
> wrote:
> >
> > Unsubscribe
> >
> > On Fri, 10 May 2024 at 10:26 PM, Aman Sinha  
> > wrote:
> >>
> >> +1 (non-binding)
> >>
> >> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju 
> >>  wrote:
> >>>
> >>> +1(non-binding)
> >>>
> >>> Thanks
> >>> Mahesh Raju S
> >>>
> >>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
> 
>  Hi All,
>  Following the discussion at [1]. Starting the official vote thread to
>  mark Hive 2.x release line as EOL.
> 
>  Marking a release lines as EOL means there won't be any further
>  release made for that release line
> 
>  I will start with my +1
> 
>  -Ayush
> 
> 
>  [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d

Re: Voice Of Apache interview request

[Bowen, Rich]

Unfortunately, the 29th is the day that I will be traveling to Bratislava for 
Community Over Code, so we’ll either need to do before that, or wait until 
after June 10th.

—Rich

> On May 16, 2024, at 3:51 AM, Stamatis Zampetakis  wrote:
> 
> An in person interview would be awesome but unfortunately I am not
> going to Bratislava.
> 
> I am in UTC+2 so how about doing Wednesday, 29 May 2024, 13:00:00 UTC
> [1]? Feel free to propose another slot if this doesn't work for you or
> if others want to join as well.
> 
> Best,
> Stamatis
> 
> [1] 
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024=5=29=13=0=0=195=179
> 
> On Wed, May 15, 2024 at 5:35 PM Bowen, Rich  wrote:
>> 
>> Thanks for being willing. I do these interviews on Google Meet, so that I 
>> can record both sides. What time zone are you in? I’m in Eastern US (New 
>> York) time (UTC -4)
>> 
>> Another option is to do the interview in person in Bratislava, if you are 
>> coming to Community Over Code next month.
>> 
>> —Rich
>> 
>>> On May 4, 2024, at 9:04 AM, Stamatis Zampetakis  wrote:
>>> 
>>> Hey Rich,
>>> 
>>> It would be great to have a podcast about Hive and the 4.0 release so
>>> I am happy to volunteer. If there are more people willing to
>>> participate I can definitely cede my place and let others do the
>>> talking.
>>> 
>>> Best,
>>> Stamatis
>>> 
>>> On Tue, Apr 30, 2024 at 4:25 PM Rich Bowen  wrote:
 
 I saw the article on news.apache.org about your recent release of 4.0
 
 As you may know, I produce a podcast about Apache projects, at 
 https://feathercast.apache.org/  I'd very much like to do a short 
 interview about the 4.0 release, and about Hive in general, and am looking 
 for a volunteer (or possibly two?) who would be willing to do such an 
 interview.
 
 Please let me know if you're interested in speaking with me on these 
 topics. (Please copy me directly on any responses - rbo...@apache.org - as 
 I am not currently subscribed to this list.)
>> 

Re: Voice Of Apache interview request

[Stamatis Zampetakis]

An in person interview would be awesome but unfortunately I am not
going to Bratislava.

I am in UTC+2 so how about doing Wednesday, 29 May 2024, 13:00:00 UTC
[1]? Feel free to propose another slot if this doesn't work for you or
if others want to join as well.

Best,
Stamatis

[1] 
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024=5=29=13=0=0=195=179

On Wed, May 15, 2024 at 5:35 PM Bowen, Rich  wrote:
>
> Thanks for being willing. I do these interviews on Google Meet, so that I can 
> record both sides. What time zone are you in? I’m in Eastern US (New York) 
> time (UTC -4)
>
> Another option is to do the interview in person in Bratislava, if you are 
> coming to Community Over Code next month.
>
> —Rich
>
> > On May 4, 2024, at 9:04 AM, Stamatis Zampetakis  wrote:
> >
> > Hey Rich,
> >
> > It would be great to have a podcast about Hive and the 4.0 release so
> > I am happy to volunteer. If there are more people willing to
> > participate I can definitely cede my place and let others do the
> > talking.
> >
> > Best,
> > Stamatis
> >
> > On Tue, Apr 30, 2024 at 4:25 PM Rich Bowen  wrote:
> >>
> >> I saw the article on news.apache.org about your recent release of 4.0
> >>
> >> As you may know, I produce a podcast about Apache projects, at 
> >> https://feathercast.apache.org/  I'd very much like to do a short 
> >> interview about the 4.0 release, and about Hive in general, and am looking 
> >> for a volunteer (or possibly two?) who would be willing to do such an 
> >> interview.
> >>
> >> Please let me know if you're interested in speaking with me on these 
> >> topics. (Please copy me directly on any responses - rbo...@apache.org - as 
> >> I am not currently subscribed to this list.)
>

Re: Voice Of Apache interview request

[Bowen, Rich]

Thanks for being willing. I do these interviews on Google Meet, so that I can 
record both sides. What time zone are you in? I’m in Eastern US (New York) time 
(UTC -4)

Another option is to do the interview in person in Bratislava, if you are 
coming to Community Over Code next month.

—Rich

> On May 4, 2024, at 9:04 AM, Stamatis Zampetakis  wrote:
> 
> Hey Rich,
> 
> It would be great to have a podcast about Hive and the 4.0 release so
> I am happy to volunteer. If there are more people willing to
> participate I can definitely cede my place and let others do the
> talking.
> 
> Best,
> Stamatis
> 
> On Tue, Apr 30, 2024 at 4:25 PM Rich Bowen  wrote:
>> 
>> I saw the article on news.apache.org about your recent release of 4.0
>> 
>> As you may know, I produce a podcast about Apache projects, at 
>> https://feathercast.apache.org/  I'd very much like to do a short interview 
>> about the 4.0 release, and about Hive in general, and am looking for a 
>> volunteer (or possibly two?) who would be willing to do such an interview.
>> 
>> Please let me know if you're interested in speaking with me on these topics. 
>> (Please copy me directly on any responses - rbo...@apache.org - as I am not 
>> currently subscribed to this list.)

Re: [VOTE] Mark Hive 2.x EOL

[Naveen Gangam]

+1 Totally

On Tue, May 14, 2024 at 3:30 AM Zoltán Rátkai 
wrote:

> +1 (non-binding)
>
> Regards,
>
> Zoltan Ratkai
>
> On Tue, May 14, 2024 at 5:42 AM Sourabh Badhya
>  wrote:
>
>> +1 (non-binding)
>>
>> Regards,
>> Sourabh Badhya
>>
>> On Mon, May 13, 2024 at 10:31 PM Krisztian Kasa
>>  wrote:
>>
>>> +1 (binding)
>>>
>>> On Mon, May 13, 2024 at 4:55 PM Okumin  wrote:
>>>
 +1 (non-binding)

 I appreciate the community's efforts in maintaining 2.x for so long.

 Thanks,
 Okumin

 On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta 
 wrote:
 >
 > Unsubscribe
 >
 > On Fri, 10 May 2024 at 10:26 PM, Aman Sinha 
 wrote:
 >>
 >> +1 (non-binding)
 >>
 >> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju <
 maheshra...@cloudera.com.invalid> wrote:
 >>>
 >>> +1(non-binding)
 >>>
 >>> Thanks
 >>> Mahesh Raju S
 >>>
 >>> On Fri, 10 May 2024, 06:15 Ayush Saxena, 
 wrote:
 
  Hi All,
  Following the discussion at [1]. Starting the official vote thread
 to
  mark Hive 2.x release line as EOL.
 
  Marking a release lines as EOL means there won't be any further
  release made for that release line
 
  I will start with my +1
 
  -Ayush
 
 
  [1]
 https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d

>>>

Re:Re: Next Hive 4.0.1 minor release

[dengzhhu653]

Thank you for your feedback and testing, Okumin! I've tagged them with 
"hive-4.0.1-must".




Thanks,

Zhihua

At 2024-05-15 10:43:59, "Okumin"  wrote:
>Hi Zhihua,
>
>Thanks for driving the next release. We are actively testing 4.0.0 and
>would like to give some suggestions.
>
># HIVE-27847: Prevent query Failures on Numeric <-> Timestamp
>We hit the issue when we ran Hive 4 with the option. I believe it is
>worth resolving for those who want to try Hive 4, keeping
>compatibilities with a previous version.
>https://issues.apache.org/jira/browse/HIVE-27847
>
># HIVE-28098: Fails to copy empty column statistics of materialized CTE
>This follows up on HIVE-28080, but the current 4.0.0 includes only
>HIVE-28080. The reasonable option to me is to revert HIVE-28080 or
>cherry-pick HIVE-28098, all or nothing.
>https://issues.apache.org/jira/browse/HIVE-28098
>
>Thanks,
>Okumin
>
>On Sat, May 11, 2024 at 9:45 AM dengzhhu653  wrote:
>>
>> Hello Community,
>>
>>
>> As you have noticed, we are going to propose the next 4.0.1 release on top 
>> of 4.0.0, with some
>>
>> critical bug fixes and improvements [1]. As of now we are putting the label 
>> "hive-4.0.1-must" on the tickets
>>
>> and we plan to make sure those get c-picked to branch-4.0 [2]. Please 
>> suggest other important fixes that can be
>>
>> included in this release if any.
>>
>>
>> We will get this minor release out as soon as possible once all the tickets 
>> marked with "hive-4.0.1-must" get resolved and tested.
>>
>>
>> [1] https://lists.apache.org/thread/rkw2toj5d74t8n5jvnkrfw77hyzn7qh3
>>
>> [2] 
>> https://issues.apache.org/jira/browse/HIVE-28204?jql=labels%20%3D%20hive-4.0.1-must
>>
>>
>> Thanks,
>>
>> Zhihua

Re: Next Hive 4.0.1 minor release

[Okumin]

Hi Zhihua,

Thanks for driving the next release. We are actively testing 4.0.0 and
would like to give some suggestions.

# HIVE-27847: Prevent query Failures on Numeric <-> Timestamp
We hit the issue when we ran Hive 4 with the option. I believe it is
worth resolving for those who want to try Hive 4, keeping
compatibilities with a previous version.
https://issues.apache.org/jira/browse/HIVE-27847

# HIVE-28098: Fails to copy empty column statistics of materialized CTE
This follows up on HIVE-28080, but the current 4.0.0 includes only
HIVE-28080. The reasonable option to me is to revert HIVE-28080 or
cherry-pick HIVE-28098, all or nothing.
https://issues.apache.org/jira/browse/HIVE-28098

Thanks,
Okumin

On Sat, May 11, 2024 at 9:45 AM dengzhhu653  wrote:
>
> Hello Community,
>
>
> As you have noticed, we are going to propose the next 4.0.1 release on top of 
> 4.0.0, with some
>
> critical bug fixes and improvements [1]. As of now we are putting the label 
> "hive-4.0.1-must" on the tickets
>
> and we plan to make sure those get c-picked to branch-4.0 [2]. Please suggest 
> other important fixes that can be
>
> included in this release if any.
>
>
> We will get this minor release out as soon as possible once all the tickets 
> marked with "hive-4.0.1-must" get resolved and tested.
>
>
> [1] https://lists.apache.org/thread/rkw2toj5d74t8n5jvnkrfw77hyzn7qh3
>
> [2] 
> https://issues.apache.org/jira/browse/HIVE-28204?jql=labels%20%3D%20hive-4.0.1-must
>
>
> Thanks,
>
> Zhihua

Community over Code EU 2024: The countdown has started!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

We are very close to Community Over Code EU -- check out the amazing
program and the special discounts that we have for you.

Special discounts

You still have the opportunity to secure your ticket for Community
Over Code EU. Explore the various options available, including the
regular pass, the committer and groups pass, and now introducing the
one-day pass tailored for locals in Bratislava.

We also have a special discount for you to attend both Community Over
Code and Berlin Buzzwords from June 9th to 11th. Visit our website to
find out more about this opportunity and contact te...@sg.com.mx to
get the discount code.

Take advantage of the discounts and register now!
https://eu.communityovercode.org/tickets/

Check out the full program!

This year Community Over Code Europe will bring to you three days of
keynotes and sessions that cover topics of interest for ASF projects
and the greater open source ecosystem including data engineering,
performance engineering, search, Internet of Things (IoT) as well as
sessions with tips and lessons learned on building a healthy open
source community.

Check out the program: https://eu.communityovercode.org/program/

Keynote speaker highlights for Community Over Code Europe include:

* Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software
Foundation, will discuss the Cyber Resiliency Act and its impact on
open source (All your code belongs to Policy Makers, Politicians, and
the Law).

* Dr. Sherae Daniel will share the results of her study on the impact
of self-promotion for open source software developers (To Toot or not
to Toot, that is the question).

* Asim Hussain, Executive Director of the Green Software Foundation
will present a framework they have developed for quantifying the
environmental impact of software (Doing for Sustainability what Open
Source did for Software).

* Ruth Ikegah will  discuss the growth of the open source movement in
Africa (From Local Roots to Global Impact: Building an Inclusive Open
Source Community in Africa)

* A discussion panel on EU policies and regulations affecting
specialists working in Open Source Program Offices

Additional activities

* Poster sessions: We invite you to stop by our poster area and see if
the ideas presented ignite a conversation within your team.

* BOF time: Don't miss the opportunity to discuss in person with your
open source colleagues on your shared interests.

* Participants reception: At the end of the first day, we will have a
reception at the event venue. All participants are welcome to attend!

* Spontaneous talks: There is a dedicated room and social space for
having spontaneous talks and sessions. Get ready to share with your
peers.

* Lighting talks: At the end of the event we will have the awaited
Lighting talks, where every participant is welcome to share and
enlighten us.

Please remember:  If you haven't applied for the visa, we will provide
the necessary letter for the process. In the unfortunate case of a
visa rejection, your ticket will be reimbursed.

See you in Bratislava,

Community Over Code EU Team

Re: [VOTE] Mark Hive 2.x EOL

[Zoltán Rátkai]

+1 (non-binding)

Regards,

Zoltan Ratkai

On Tue, May 14, 2024 at 5:42 AM Sourabh Badhya 
wrote:

> +1 (non-binding)
>
> Regards,
> Sourabh Badhya
>
> On Mon, May 13, 2024 at 10:31 PM Krisztian Kasa 
> wrote:
>
>> +1 (binding)
>>
>> On Mon, May 13, 2024 at 4:55 PM Okumin  wrote:
>>
>>> +1 (non-binding)
>>>
>>> I appreciate the community's efforts in maintaining 2.x for so long.
>>>
>>> Thanks,
>>> Okumin
>>>
>>> On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta 
>>> wrote:
>>> >
>>> > Unsubscribe
>>> >
>>> > On Fri, 10 May 2024 at 10:26 PM, Aman Sinha 
>>> wrote:
>>> >>
>>> >> +1 (non-binding)
>>> >>
>>> >> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju <
>>> maheshra...@cloudera.com.invalid> wrote:
>>> >>>
>>> >>> +1(non-binding)
>>> >>>
>>> >>> Thanks
>>> >>> Mahesh Raju S
>>> >>>
>>> >>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
>>> 
>>>  Hi All,
>>>  Following the discussion at [1]. Starting the official vote thread
>>> to
>>>  mark Hive 2.x release line as EOL.
>>> 
>>>  Marking a release lines as EOL means there won't be any further
>>>  release made for that release line
>>> 
>>>  I will start with my +1
>>> 
>>>  -Ayush
>>> 
>>> 
>>>  [1]
>>> https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>>>
>>

Re: [VOTE] Mark Hive 2.x EOL

[Sourabh Badhya]

+1 (non-binding)

Regards,
Sourabh Badhya

On Mon, May 13, 2024 at 10:31 PM Krisztian Kasa 
wrote:

> +1 (binding)
>
> On Mon, May 13, 2024 at 4:55 PM Okumin  wrote:
>
>> +1 (non-binding)
>>
>> I appreciate the community's efforts in maintaining 2.x for so long.
>>
>> Thanks,
>> Okumin
>>
>> On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta 
>> wrote:
>> >
>> > Unsubscribe
>> >
>> > On Fri, 10 May 2024 at 10:26 PM, Aman Sinha 
>> wrote:
>> >>
>> >> +1 (non-binding)
>> >>
>> >> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju <
>> maheshra...@cloudera.com.invalid> wrote:
>> >>>
>> >>> +1(non-binding)
>> >>>
>> >>> Thanks
>> >>> Mahesh Raju S
>> >>>
>> >>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
>> 
>>  Hi All,
>>  Following the discussion at [1]. Starting the official vote thread to
>>  mark Hive 2.x release line as EOL.
>> 
>>  Marking a release lines as EOL means there won't be any further
>>  release made for that release line
>> 
>>  I will start with my +1
>> 
>>  -Ayush
>> 
>> 
>>  [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>>
>

Re: [VOTE] Mark Hive 2.x EOL

[Krisztian Kasa]

+1 (binding)

On Mon, May 13, 2024 at 4:55 PM Okumin  wrote:

> +1 (non-binding)
>
> I appreciate the community's efforts in maintaining 2.x for so long.
>
> Thanks,
> Okumin
>
> On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta 
> wrote:
> >
> > Unsubscribe
> >
> > On Fri, 10 May 2024 at 10:26 PM, Aman Sinha 
> wrote:
> >>
> >> +1 (non-binding)
> >>
> >> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju <
> maheshra...@cloudera.com.invalid> wrote:
> >>>
> >>> +1(non-binding)
> >>>
> >>> Thanks
> >>> Mahesh Raju S
> >>>
> >>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
> 
>  Hi All,
>  Following the discussion at [1]. Starting the official vote thread to
>  mark Hive 2.x release line as EOL.
> 
>  Marking a release lines as EOL means there won't be any further
>  release made for that release line
> 
>  I will start with my +1
> 
>  -Ayush
> 
> 
>  [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>

Re: [VOTE] Mark Hive 2.x EOL

[Okumin]

+1 (non-binding)

I appreciate the community's efforts in maintaining 2.x for so long.

Thanks,
Okumin

On Sat, May 11, 2024 at 1:57 AM Abhishek Gupta  wrote:
>
> Unsubscribe
>
> On Fri, 10 May 2024 at 10:26 PM, Aman Sinha  wrote:
>>
>> +1 (non-binding)
>>
>> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju 
>>  wrote:
>>>
>>> +1(non-binding)
>>>
>>> Thanks
>>> Mahesh Raju S
>>>
>>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:

 Hi All,
 Following the discussion at [1]. Starting the official vote thread to
 mark Hive 2.x release line as EOL.

 Marking a release lines as EOL means there won't be any further
 release made for that release line

 I will start with my +1

 -Ayush


 [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d

Next Hive 4.0.1 minor release

[dengzhhu653]

Hello Community, 




As you have noticed, we are going to propose the next 4.0.1 release on top of 
4.0.0, with some

critical bug fixes and improvements [1]. As of now we are putting the label 
"hive-4.0.1-must" on the tickets

and we plan to make sure those get c-picked to branch-4.0 [2]. Please suggest 
other important fixes that can be 

included in this release if any.




We will get this minor release out as soon as possible once all the tickets 
marked with "hive-4.0.1-must" get resolved and tested.




[1] https://lists.apache.org/thread/rkw2toj5d74t8n5jvnkrfw77hyzn7qh3

[2] 
https://issues.apache.org/jira/browse/HIVE-28204?jql=labels%20%3D%20hive-4.0.1-must




Thanks,

Zhihua

Re: [VOTE] Mark Hive 2.x EOL

[Abhishek Gupta]

Unsubscribe

On Fri, 10 May 2024 at 10:26 PM, Aman Sinha  wrote:

> +1 (non-binding)
>
> On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju
>  wrote:
>
>> +1(non-binding)
>>
>> Thanks
>> Mahesh Raju S
>>
>> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
>>
>>> Hi All,
>>> Following the discussion at [1]. Starting the official vote thread to
>>> mark Hive 2.x release line as EOL.
>>>
>>> Marking a release lines as EOL means there won't be any further
>>> release made for that release line
>>>
>>> I will start with my +1
>>>
>>> -Ayush
>>>
>>>
>>> [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>>>
>>

Re: [VOTE] Mark Hive 2.x EOL

[Aman Sinha]

+1 (non-binding)

On Fri, May 10, 2024 at 7:57 AM Mahesh Raju Somalaraju
 wrote:

> +1(non-binding)
>
> Thanks
> Mahesh Raju S
>
> On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:
>
>> Hi All,
>> Following the discussion at [1]. Starting the official vote thread to
>> mark Hive 2.x release line as EOL.
>>
>> Marking a release lines as EOL means there won't be any further
>> release made for that release line
>>
>> I will start with my +1
>>
>> -Ayush
>>
>>
>> [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>>
>

Re: [VOTE] Mark Hive 2.x EOL

[Mahesh Raju Somalaraju]

+1(non-binding)

Thanks
Mahesh Raju S

On Fri, 10 May 2024, 06:15 Ayush Saxena,  wrote:

> Hi All,
> Following the discussion at [1]. Starting the official vote thread to
> mark Hive 2.x release line as EOL.
>
> Marking a release lines as EOL means there won't be any further
> release made for that release line
>
> I will start with my +1
>
> -Ayush
>
>
> [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>

Re: [VOTE] Mark Hive 2.x EOL

[Chao Sun]

(+1) binding

On Fri, May 10, 2024 at 4:40 AM kokila narayanan <
kokilanarayana...@gmail.com> wrote:

> +1(non-binding)
>
> Thanks
> Kokila
>
> On Fri, 10 May, 2024, 17:07 Simhadri G,  wrote:
>
>> +1 (non-binding)
>>
>>
>> On Fri, May 10, 2024 at 2:34 PM Stamatis Zampetakis 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> On Fri, May 10, 2024 at 10:10 AM Denys Kuzmenko 
>>> wrote:
>>> >
>>> > +1 (binding)
>>>
>>

Re: [VOTE] Mark Hive 2.x EOL

[kokila narayanan]

+1(non-binding)

Thanks
Kokila

On Fri, 10 May, 2024, 17:07 Simhadri G,  wrote:

> +1 (non-binding)
>
>
> On Fri, May 10, 2024 at 2:34 PM Stamatis Zampetakis 
> wrote:
>
>> +1 (binding)
>>
>> On Fri, May 10, 2024 at 10:10 AM Denys Kuzmenko 
>> wrote:
>> >
>> > +1 (binding)
>>
>

Re: [VOTE] Mark Hive 2.x EOL

[Simhadri G]

+1 (non-binding)


On Fri, May 10, 2024 at 2:34 PM Stamatis Zampetakis 
wrote:

> +1 (binding)
>
> On Fri, May 10, 2024 at 10:10 AM Denys Kuzmenko 
> wrote:
> >
> > +1 (binding)
>

Re: [VOTE] Mark Hive 2.x EOL

[Stamatis Zampetakis]

+1 (binding)

On Fri, May 10, 2024 at 10:10 AM Denys Kuzmenko  wrote:
>
> +1 (binding)

Re: [VOTE] Mark Hive 2.x EOL

[Denys Kuzmenko]

+1 (binding)

Re: [VOTE] Mark Hive 2.x EOL

[Attila Turoczy]

+1 (non-binding)

-Attila

On Fri, 10 May 2024 at 03:20, Butao Zhang  wrote:

> +1
>
>
> Thanks
> Butao Zhang
>  Replied Message 
> From Ayush Saxena 
> Date 5/10/2024 08:45
> To dev 
> Subject [VOTE] Mark Hive 2.x EOL
> Hi All,
> Following the discussion at [1]. Starting the official vote thread to
> mark Hive 2.x release line as EOL.
>
> Marking a release lines as EOL means there won't be any further
> release made for that release line
>
> I will start with my +1
>
> -Ayush
>
>
> [1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d
>

Re: [VOTE] Mark Hive 2.x EOL

[Butao Zhang]

+1





Thanks
Butao Zhang
 Replied Message 
| From | Ayush Saxena |
| Date | 5/10/2024 08:45 |
| To | dev |
| Subject | [VOTE] Mark Hive 2.x EOL |
Hi All,
Following the discussion at [1]. Starting the official vote thread to
mark Hive 2.x release line as EOL.

Marking a release lines as EOL means there won't be any further
release made for that release line

I will start with my +1

-Ayush


[1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d

[VOTE] Mark Hive 2.x EOL

[Ayush Saxena]

Hi All,
Following the discussion at [1]. Starting the official vote thread to
mark Hive 2.x release line as EOL.

Marking a release lines as EOL means there won't be any further
release made for that release line

I will start with my +1

-Ayush


[1] https://lists.apache.org/thread/91wk3oy1qo953md7941ojg2q97ofsl2d

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

[Ayush Saxena]

We have had the last 2.x release. I don't think we did c-pick our
security issues into the last release either.
 Will start the EOL vote for the 2.x release line as we discussed earlier

-Ayush

On Sun, 21 Apr 2024 at 01:33, Chao Sun  wrote:
>
> Hi Cheng,
>
> Sorry for the long delay. I was distracted by other things.
>
> I just created RC0 for the Hive 2.3.10 release, and started a vote thread. 
> Please help to test if it looks good, especially from Spark side. Thanks!
>
> Best,
> Chao
>
>
>
> On Thu, Apr 18, 2024 at 5:15 AM Cheng Pan  wrote:
>>
>> Hi Chao,
>>
>> The Spark community is starting to discuss the 4.0 release[1], can we make 
>> the Hive 2.3.10 release happen soon?
>>
>> [1] https://lists.apache.org/thread/nxmvz2j7kp96otzlnl3kd277knlb6qgb
>>
>> Thanks,
>> Cheng Pan
>>
>> On 2024/01/17 17:50:37 Chao Sun wrote:
>> > Hi Ayush,
>> >
>> > I'm working on the last few commits to backport to the branch.
>> > Hopefully within 1-2 months I can start the release process. Our goal
>> > is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this
>> > year.
>> >
>> > Chao
>> >
>> > On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena  wrote:
>> > >
>> > > Thanx everyone for the feedback, I have started a formal thread to mark 
>> > > 1.x
>> > > EOL. We can have one last release for 2.x as Chao mentioned, with some
>> > > required changes + our CVE's & get the release line marked as EOL then.
>> > >
>> > > @Chao Sun  Do let us know if you have a proposed
>> > > timeline for that.
>> > >
>> > > -Ayush
>> > >
>> > > On Wed, 17 Jan 2024 at 08:23, vihang karajgaonkar 
>> > > wrote:
>> > >
>> > > > I was confused about the subject line since it says 3.x as well along 
>> > > > with
>> > > > 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or just 
>> > > > 1.x
>> > > > and 2.x?
>> > > >
>> > > > I think it makes sense to EOL 1.x. Looks like 2.x is still being 
>> > > > maintained
>> > > > by Chao and I think we were backporting PRs to the 3.x line pretty 
>> > > > recently
>> > > > so I believe we should wait out for a release on Hive 3.x.
>> > > >
>> > > > Thanks,
>> > > > Vihang
>> > > >
>> > > > On Tue, Jan 16, 2024 at 3:40 PM Attila Turoczy
>> > > >  wrote:
>> > > >
>> > > > > Dear PMC's,
>> > > > >
>> > > > > Do we have a verdict / decision about this?
>> > > > >
>> > > > > -Attila
>> > > > >
>> > > > > On Wed, Jan 10, 2024 at 5:45 PM Chao Sun  wrote:
>> > > > >
>> > > > > > On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 
>> > > > > > 2.3
>> > > > > > branch is being actively maintained so far). Hopefully this will be
>> > > > > > the last release in the branch-2 line.
>> > > > > >
>> > > > > > +1 on making Hive 1 EOL for the time being.
>> > > > > >
>> > > > > > Chao
>> > > > > >
>> > > > > > On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan
>> > > > > >  wrote:
>> > > > > > >
>> > > > > > > +1 for making both Hive 1&2 EOL
>> > > > > > >
>> > > > > > > -Sankar
>> > > > > > > -Original Message-
>> > > > > > > From: Attila Turoczy 
>> > > > > > > Sent: Wednesday, January 10, 2024 7:37 PM
>> > > > > > > To: dev@hive.apache.org
>> > > > > > > Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, 
>> > > > > > > 3.x
>> > > > > > >
>> > > > > > > [You don't often get email from aturo...@cloudera.com.invalid. 
>> > > > > > > Learn
>> > > > > > why this is important at 
>> > > > > > https://aka.ms/LearnAboutSenderIdentification
>> > > > ]
>> > > > > > >
>> > > > > > > +1 for making it EOL for Hive 1 and Hive 2. I do not think these 
>> > > > > > > 2
>> > > > > > product
>> > > > > > > branches are relevant in 2023.
>> > > > > > >
>> > > > > > > -Attila
>> > > > > > >
>> > > > > > > On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko <
>> > > > dkuzme...@apache.org>
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > > +1 for marking Hive 1.x EOL
>> > > > > > > >
>> > > > > > > > Assuming no volunteers willing to take ownership of branch-2
>> > > > > > maintenance,
>> > > > > > > > +1 to declare it EOL as well.
>> > > > > > > >
>> > > > > > > > Regards,
>> > > > > > > > Denys
>> > > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> >
>>
>>
>>

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 1

[Chao Sun]

+1 (binding) myself.

Thanks everyone! The vote passed with 3 binding votes (Rui, Szehon and
Chao), and 2 non-binding votes from Cheng and Dongjoon. I'll proceed to
publish the release as the next step.

Chao

On Tue, May 7, 2024 at 12:45 PM Szehon Ho  wrote:

> +1 (binding)
>
> - Checked checksums
> - Built from source
> - Create and query simple table
> - It seems some basic query print an ugly warning, but still pass in the
> end.  Not sure if need to change some config.
>
> 0: jdbc:hive2://> insert into test select 1;
> 24/05/07 12:40:34 [537b5f20-dd1a-4be6-af09-effa6d9d37a5 main]: ERROR
> parse.CalcitePlanner: CBO failed, skipping CBO.
> org.apache.hadoop.hive.ql.optimizer.calcite.CalciteSemanticException:
> Unsupported
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.genLogicalPlan(CalcitePlanner.java:3974)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1315)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1261)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.calcite.tools.Frameworks$1.apply(Frameworks.java:113)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.calcite.prepare.CalcitePrepareImpl.perform(CalcitePrepareImpl.java:997)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:149)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.calcite.tools.Frameworks.withPlanner(Frameworks.java:106)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.logicalPlan(CalcitePlanner.java:1069)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.getOptimizedAST(CalcitePlanner.java:1085)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:364)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11138)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:286)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:258)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:512)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1317)
> ~[hive-exec-2.3.10.jar:2.3.10]
> at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1295)
> ~[hive-exec-2.3.10.jar:2.3.10]
>
> Thanks
> Szehon
>
> On Tue, May 7, 2024 at 1:11 AM Rui Li  wrote:
>
>> +1 (binding)
>>
>> - Built from source
>> - Verified signature and checksum
>> - Ran some basic SQL statements
>> - Verified the fix made in https://github.com/apache/hive/pull/5204
>>
>> Thanks Chao for driving this.
>>
>> On Tue, May 7, 2024 at 2:26 AM Dongjoon Hyun  wrote:
>>
>>> +1 (non-binding)
>>>
>>> Thank you so much all!
>>>
>>> Dongjoon.
>>>
>>> On 2024/05/06 13:57:09 Cheng Pan wrote:
>>> > +1 (non-binding)
>>> >
>>> > Pass integration test with Apache Spark[1] and Apache Kyuubi[2].
>>> >
>>> > [1] https://github.com/apache/spark/pull/45372
>>> > [2] https://github.com/apache/kyuubi/pull/6328
>>> >
>>> > Thanks,
>>> > Cheng Pan
>>> >
>>> >
>>> >
>>>
>>
>>
>> --
>> Cheers,
>> Rui Li
>>
>

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 1

[Szehon Ho]

+1 (binding)

- Checked checksums
- Built from source
- Create and query simple table
- It seems some basic query print an ugly warning, but still pass in the
end.  Not sure if need to change some config.

0: jdbc:hive2://> insert into test select 1;
24/05/07 12:40:34 [537b5f20-dd1a-4be6-af09-effa6d9d37a5 main]: ERROR
parse.CalcitePlanner: CBO failed, skipping CBO.
org.apache.hadoop.hive.ql.optimizer.calcite.CalciteSemanticException:
Unsupported
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.genLogicalPlan(CalcitePlanner.java:3974)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1315)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner$CalcitePlannerAction.apply(CalcitePlanner.java:1261)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.calcite.tools.Frameworks$1.apply(Frameworks.java:113)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.calcite.prepare.CalcitePrepareImpl.perform(CalcitePrepareImpl.java:997)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.calcite.tools.Frameworks.withPrepare(Frameworks.java:149)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.calcite.tools.Frameworks.withPlanner(Frameworks.java:106)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.logicalPlan(CalcitePlanner.java:1069)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.getOptimizedAST(CalcitePlanner.java:1085)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:364)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11138)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:286)
~[hive-exec-2.3.10.jar:2.3.10]
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:258)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:512)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1317)
~[hive-exec-2.3.10.jar:2.3.10]
at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1295)
~[hive-exec-2.3.10.jar:2.3.10]

Thanks
Szehon

On Tue, May 7, 2024 at 1:11 AM Rui Li  wrote:

> +1 (binding)
>
> - Built from source
> - Verified signature and checksum
> - Ran some basic SQL statements
> - Verified the fix made in https://github.com/apache/hive/pull/5204
>
> Thanks Chao for driving this.
>
> On Tue, May 7, 2024 at 2:26 AM Dongjoon Hyun  wrote:
>
>> +1 (non-binding)
>>
>> Thank you so much all!
>>
>> Dongjoon.
>>
>> On 2024/05/06 13:57:09 Cheng Pan wrote:
>> > +1 (non-binding)
>> >
>> > Pass integration test with Apache Spark[1] and Apache Kyuubi[2].
>> >
>> > [1] https://github.com/apache/spark/pull/45372
>> > [2] https://github.com/apache/kyuubi/pull/6328
>> >
>> > Thanks,
>> > Cheng Pan
>> >
>> >
>> >
>>
>
>
> --
> Cheers,
> Rui Li
>

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 1

[Rui Li]

+1 (binding)

- Built from source
- Verified signature and checksum
- Ran some basic SQL statements
- Verified the fix made in https://github.com/apache/hive/pull/5204

Thanks Chao for driving this.

On Tue, May 7, 2024 at 2:26 AM Dongjoon Hyun  wrote:

> +1 (non-binding)
>
> Thank you so much all!
>
> Dongjoon.
>
> On 2024/05/06 13:57:09 Cheng Pan wrote:
> > +1 (non-binding)
> >
> > Pass integration test with Apache Spark[1] and Apache Kyuubi[2].
> >
> > [1] https://github.com/apache/spark/pull/45372
> > [2] https://github.com/apache/kyuubi/pull/6328
> >
> > Thanks,
> > Cheng Pan
> >
> >
> >
>


-- 
Cheers,
Rui Li

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 1

[Dongjoon Hyun]

+1 (non-binding)

Thank you so much all!

Dongjoon.

On 2024/05/06 13:57:09 Cheng Pan wrote:
> +1 (non-binding)
> 
> Pass integration test with Apache Spark[1] and Apache Kyuubi[2].
> 
> [1] https://github.com/apache/spark/pull/45372
> [2] https://github.com/apache/kyuubi/pull/6328
> 
> Thanks,
> Cheng Pan
> 
> 
> 

[VOTE] Apache Hive 2.3.10 Release Candidate 1

[Cheng Pan]

+1 (non-binding)

Pass integration test with Apache Spark[1] and Apache Kyuubi[2].

[1] https://github.com/apache/spark/pull/45372
[2] https://github.com/apache/kyuubi/pull/6328

Thanks,
Cheng Pan

[VOTE] Apache Hive 2.3.10 Release Candidate 1

[Chao Sun]

Apache Hive 2.3.10 Release Candidate 1 is available here:
https://people.apache.org/~sunchao/apache-hive-2.3.10-rc-1/
Maven artifacts are available here:
https://repository.apache.org/content/repositories/orgapachehive-1129/
The
tag release-2.3.10-rc1 has been applied to the source for this
release in github, you can see it at
https://github.com/apache/hive/tree/release-2.3.10-rc1
Voting will conclude in 72 hours (or whenever I scrounge together enough
votes).

Hive PMC Members: Please test and vote.

Thanks.

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Chao Sun]

Thanks for the feedback. Due to the additional backports required for
2.3.10. I'm going to abandon this RC and create a new RC1 shortly.

Chao

On Wed, Apr 24, 2024 at 9:15 AM Chao Sun  wrote:

> Thanks Cheng, I'll take a look at HIVE-28121 and create another RC.
>
> > The vote email seems to have a wrong repository link, 1106. IIUC, 1128
> is the valid one, isn't it?
>
> Oops. Yes it should be 1128. I reused the email content from my previous
> release but forgot to change the link. Sorry about that.
>
> Chao
>
> On Wed, Apr 24, 2024 at 9:08 AM Dongjoon Hyun  wrote:
>
>> Hi, Chao.
>>
>> The vote email seems to have a wrong repository link, 1106. IIUC, 1128 is
>> the valid one, isn't it?
>>
>> Dongjoon.
>>
>> On 2024/04/20 20:01:53 Chao Sun wrote:
>> > Apache Hive 2.3.10 Release Candidate 0 is available here:
>> > https://people.apache.org/~sunchao/apache-hive-2.3.10-rc-0/
>> > Maven artifacts are available here:
>> > https://repository.apache.org/content/repositories/orgapachehive-1128
>> > > >The
>> > tag release-2.3.10-rc0 has been applied to the source for this
>> > release in github, you can see it at
>> > https://github.com/apache/hive/tree/release-2.3.10-rc0
>> > Voting will conclude in 72 hours (or whenever I scrounge together enough
>> > votes).
>> >
>> > Hive PMC Members: Please test and vote.
>> >
>> > Thanks.
>> >
>>
>

Re: Voice Of Apache interview request

[Stamatis Zampetakis]

Hey Rich,

It would be great to have a podcast about Hive and the 4.0 release so
I am happy to volunteer. If there are more people willing to
participate I can definitely cede my place and let others do the
talking.

Best,
Stamatis

On Tue, Apr 30, 2024 at 4:25 PM Rich Bowen  wrote:
>
> I saw the article on news.apache.org about your recent release of 4.0
>
> As you may know, I produce a podcast about Apache projects, at 
> https://feathercast.apache.org/  I'd very much like to do a short interview 
> about the 4.0 release, and about Hive in general, and am looking for a 
> volunteer (or possibly two?) who would be willing to do such an interview.
>
> Please let me know if you're interested in speaking with me on these topics. 
> (Please copy me directly on any responses - rbo...@apache.org - as I am not 
> currently subscribed to this list.)

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

[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

[Zoltan Haindrich]

I think the shading should be fixed instead restoring this core jar.
Providing a core-jar means that we support it and I think that would be a bad 
move:
I believe its an irrational expectation from any project to use the same or 
compatible deps as against hive-exec was compiled!
For example hive-exec uses an ancient guava which was released back in 2017 
https://mvnrepository.com/artifact/com.google.guava/guava/22.0
and has 3 CVEs listed... and that's just one from many deps the core-jar will 
pull into a build.
Also note that guava tends to break api quite frequently - so I guess anyone 
using a bit more recent guava will have a hard time consuming the artifact

Downstream projects have had the opportunity to try and report issues with the 
alpha releases before the 4.0 have came out or not?
If they were not doing that - I think that's not our fault!

Middle ground could be to suggest them to try the shaded hive-exec jar (we still have nightly builds [1]); notify these projects to try it and report back issues - give 
them some time fix up any further shading issues and done.


[1] http://ci.hive.apache.org/job/hive-nightly/

cheers,
Zoltan

On 4/29/24 09:16, Stamatis Zampetakis wrote:
I shared the reasons behind the removal of the jar and my concerns around bringing it back. I'm still not convinced that it's needed but if the rest of the community feels 
that it's the right path forward then I am ok with this.


Best,
Stamatis

On Fri, Apr 26, 2024, 2:42 PM Ayush Saxena mailto:ayush...@gmail.com>> wrote:

Stamatis,
Isn't the removal itself an incompatible change? There are a lot of projects 
using it & we suddenly removed a jar because there were some people not sure 
how to
properly use it and were complaining about it.

What about the projects which are now stuck? reading the thread at [1], 
there were promises made that everything will be relocated and sorted before 
the release, but we
couldn't, AFAIK it isn't a naive task to just relocate all the dependencies.

As I see here @Chao Sun , even raised concerns [2], that the removal just 
stops the way for upgrading downstream projects and it got countered like folks 
chasing the
removal will help chase getting all the dependencies relocated or solve the 
issues for downstream. I think none volunteered.

I would either recommend:
* Best case we relocate all the dependencies present in hive-exec, not just one or 
two. Somebody volunteers to raise one PR relocating "all" and we can commit 
that and
we should be sorted.
* Restore back the core jar, because a lot of projects depend on it, the 
removal itself was incompatible, the removal I don't think had a clear 
community agreement, it
was a conditional agreement, which I don't think got sorted, so we should 
rollback.

On a lighter note, we might release with some 5000+ commits, with best 
performance or so, but if nobody is able to consume those release bits, I think 
those efforts are
just getting waste, eventually people will just stick to their older versions 
and not even try to upgrade & we will be releasing for nobody or maybe for few 
folks who
just have only Hive in their stack (I don't know if there are folks like 
that), No matter how good a product is, if people don't use it, it is gonna die 
:-(


I think we have a ticket which talks about relocating all dependencies, I 
agree we should drop the core jar for sure, it leads to all the problems as 
Stamatis mentioned
but lets restore the core jar back & we can drop it when that relocation 
ticket is resolved. Does that sound convincing, or even worth a thought?

btw. having jars with a set of dependencies shaded and other ones unshaded is 
done in hadoop as well, hadoop-minicluster vs hadoop-client-minicluster & such 
problems by
users keep on coming, eg [3]

Anyone else, any thoughts?

-Ayush

[1] https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg 

[2] https://lists.apache.org/thread/23sshgolmbpcc01npqgt03woljdy6hdn 

[3] https://lists.apache.org/thread/f47s6bxrtslkxbc8s2gybwrxps8vk63x 




On Fri, 26 Apr 2024 at 16:37, Stamatis Zampetakis mailto:zabe...@gmail.com>> wrote:

Hey Simhadri, thanks for starting this discussion.

Maven has many limitations when it comes to publishing multiple
artifacts from the same module. In most cases, the end result is
broken and hard to use. The pom file that is published for a given
module is not able to describe correctly all artifacts of the module
and that's why there is one main artifact for every module; dependency
declarations are usually correct for the main artifact but are not
representative for the rest.

For 

CVE-2023-35701: Apache Hive: Arbitrary command execution via JDBC driver

[Stamatis Zampetakis]

Severity: moderate

Affected versions:

- Apache Hive 4.0.0-alpha-1 before 4.0.0

Description:

Improper Control of Generation of Code ('Code Injection') vulnerability in 
Apache Hive.

The vulnerability affects the Hive JDBC driver component and it can potentially 
lead to arbitrary code execution on the machine/endpoint that the JDBC driver 
(client) is running. The malicious user must have sufficient permissions to 
specify/edit JDBC URL(s) in an endpoint relying on the Hive JDBC driver and the 
JDBC client process must run under a privileged user to fully exploit the 
vulnerability. 

The attacker can setup a malicious HTTP server and specify a JDBC URL pointing 
towards this server. When a JDBC connection is attempted, the malicious HTTP 
server can provide a special response with customized payload that can trigger 
the execution of certain commands in the JDBC client.This issue affects Apache 
Hive: from 4.0.0-alpha-1 before 4.0.0.

Users are recommended to upgrade to version 4.0.0, which fixes the issue.

This issue is being tracked as HIVE-27554 

Credit:

Kostya Kortchinsky (reporter)

References:

https://hive.apache.org/
https://www.cve.org/CVERecord?id=CVE-2023-35701
https://issues.apache.org/jira/browse/HIVE-27554

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

[Denys Kuzmenko]

Just found out that Amoro project is also using hive-exec:jar:core
+1 to restore

Voice Of Apache interview request

[Rich Bowen]

I saw the article on news.apache.org about your recent release of 4.0

As you may know, I produce a podcast about Apache projects, at 
https://feathercast.apache.org/  I'd very much like to do a short interview 
about the 4.0 release, and about Hive in general, and am looking for a 
volunteer (or possibly two?) who would be willing to do such an interview.

Please let me know if you're interested in speaking with me on these topics. 
(Please copy me directly on any responses - rbo...@apache.org - as I am not 
currently subscribed to this list.)

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

[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: [Discussion] HIVE-28211: Restore hive-exec:core jar

[Sourabh Badhya]

+1. Multiple projects will benefit from this.

Thanks Simhadri for driving this discussion.

Regards,
Sourabh Badhya

On Mon, Apr 29, 2024 at 12:46 PM Stamatis Zampetakis 
wrote:

> I shared the reasons behind the removal of the jar and my concerns around
> bringing it back. I'm still not convinced that it's needed but if the rest
> of the community feels that it's the right path forward then I am ok with
> this.
>
> Best,
> Stamatis
>
> On Fri, Apr 26, 2024, 2:42 PM Ayush Saxena  wrote:
>
>> Stamatis,
>> Isn't the removal itself an incompatible change? There are a lot of
>> projects using it & we suddenly removed a jar because there were some
>> people not sure how to properly use it and were complaining about it.
>>
>> What about the projects which are now stuck? reading the thread at [1],
>> there were promises made that everything will be relocated and sorted
>> before the release, but we couldn't, AFAIK it isn't a naive task to just
>> relocate all the dependencies.
>>
>> As I see here @Chao Sun , even raised concerns [2], that the removal just
>> stops the way for upgrading downstream projects and it got countered like
>> folks chasing the removal will help chase getting all the dependencies
>> relocated or solve the issues for downstream. I think none volunteered.
>>
>> I would either recommend:
>> * Best case we relocate all the dependencies present in hive-exec, not
>> just one or two. Somebody volunteers to raise one PR relocating "all" and
>> we can commit that and we should be sorted.
>> * Restore back the core jar, because a lot of projects depend on it, the
>> removal itself was incompatible, the removal I don't think had a clear
>> community agreement, it was a conditional agreement, which I don't think
>> got sorted, so we should rollback.
>>
>> On a lighter note, we might release with some 5000+ commits, with best
>> performance or so, but if nobody is able to consume those release bits, I
>> think those efforts are just getting waste, eventually people will just
>> stick to their older versions and not even try to upgrade & we will be
>> releasing for nobody or maybe for few folks who just have only Hive in
>> their stack (I don't know if there are folks like that), No matter how good
>> a product is, if people don't use it, it is gonna die :-(
>>
>>
>> I think we have a ticket which talks about relocating all dependencies, I
>> agree we should drop the core jar for sure, it leads to all the problems as
>> Stamatis mentioned but lets restore the core jar back & we can drop it when
>> that relocation ticket is resolved. Does that sound convincing, or even
>> worth a thought?
>>
>> btw. having jars with a set of dependencies shaded and other ones
>> unshaded is done in hadoop as well, hadoop-minicluster vs
>> hadoop-client-minicluster & such problems by users keep on coming, eg [3]
>>
>> Anyone else, any thoughts?
>>
>> -Ayush
>>
>> [1] https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg
>> [2] https://lists.apache.org/thread/23sshgolmbpcc01npqgt03woljdy6hdn
>> [3] https://lists.apache.org/thread/f47s6bxrtslkxbc8s2gybwrxps8vk63x
>>
>>
>>
>> On Fri, 26 Apr 2024 at 16:37, Stamatis Zampetakis 
>> wrote:
>>
>>> Hey Simhadri, thanks for starting this discussion.
>>>
>>> Maven has many limitations when it comes to publishing multiple
>>> artifacts from the same module. In most cases, the end result is
>>> broken and hard to use. The pom file that is published for a given
>>> module is not able to describe correctly all artifacts of the module
>>> and that's why there is one main artifact for every module; dependency
>>> declarations are usually correct for the main artifact but are not
>>> representative for the rest.
>>>
>>> For example, end-users who consume the hive-exec-core module tend to
>>> think that maven will automatically resolve all transitive
>>> dependencies and things will work as usual which is not the case. In
>>> the past, this kind of assumption created a lot of confusion on
>>> consumers of the hive-core-exec.jar with tickets and open debates that
>>> spanned for multiple months. The discussions even reached a point
>>> where people requested certain features of Hive to be reverted in
>>> order to rectify some things around transitive dependencies and the
>>> core jar.
>>>
>>> I think we should stick to the usual maven convention and just publish
>>> one artifact for each module. Adding back and claiming to support the
>>> "core" jar is a step backwards that just postpones the real problems
>>> that we need to tackle.
>>>
>>> Furthermore, I don't think that the hive-exec module was ever meant to
>>> be used as a dependency. This is mainly an application module and not
>>> a library module and that's why shading takes place. Clearly some
>>> parts from hive-exec could be considered to become a library and that
>>> would be a promising direction going forward (splitting hive-exec into
>>> other modules) but a bit outside the scope of the current discussion.
>>>
>>> 

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

[Stamatis Zampetakis]

I shared the reasons behind the removal of the jar and my concerns around
bringing it back. I'm still not convinced that it's needed but if the rest
of the community feels that it's the right path forward then I am ok with
this.

Best,
Stamatis

On Fri, Apr 26, 2024, 2:42 PM Ayush Saxena  wrote:

> Stamatis,
> Isn't the removal itself an incompatible change? There are a lot of
> projects using it & we suddenly removed a jar because there were some
> people not sure how to properly use it and were complaining about it.
>
> What about the projects which are now stuck? reading the thread at [1],
> there were promises made that everything will be relocated and sorted
> before the release, but we couldn't, AFAIK it isn't a naive task to just
> relocate all the dependencies.
>
> As I see here @Chao Sun , even raised concerns [2], that the removal just
> stops the way for upgrading downstream projects and it got countered like
> folks chasing the removal will help chase getting all the dependencies
> relocated or solve the issues for downstream. I think none volunteered.
>
> I would either recommend:
> * Best case we relocate all the dependencies present in hive-exec, not
> just one or two. Somebody volunteers to raise one PR relocating "all" and
> we can commit that and we should be sorted.
> * Restore back the core jar, because a lot of projects depend on it, the
> removal itself was incompatible, the removal I don't think had a clear
> community agreement, it was a conditional agreement, which I don't think
> got sorted, so we should rollback.
>
> On a lighter note, we might release with some 5000+ commits, with best
> performance or so, but if nobody is able to consume those release bits, I
> think those efforts are just getting waste, eventually people will just
> stick to their older versions and not even try to upgrade & we will be
> releasing for nobody or maybe for few folks who just have only Hive in
> their stack (I don't know if there are folks like that), No matter how good
> a product is, if people don't use it, it is gonna die :-(
>
>
> I think we have a ticket which talks about relocating all dependencies, I
> agree we should drop the core jar for sure, it leads to all the problems as
> Stamatis mentioned but lets restore the core jar back & we can drop it when
> that relocation ticket is resolved. Does that sound convincing, or even
> worth a thought?
>
> btw. having jars with a set of dependencies shaded and other ones unshaded
> is done in hadoop as well, hadoop-minicluster vs hadoop-client-minicluster
> & such problems by users keep on coming, eg [3]
>
> Anyone else, any thoughts?
>
> -Ayush
>
> [1] https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg
> [2] https://lists.apache.org/thread/23sshgolmbpcc01npqgt03woljdy6hdn
> [3] https://lists.apache.org/thread/f47s6bxrtslkxbc8s2gybwrxps8vk63x
>
>
>
> On Fri, 26 Apr 2024 at 16:37, Stamatis Zampetakis 
> wrote:
>
>> Hey Simhadri, thanks for starting this discussion.
>>
>> Maven has many limitations when it comes to publishing multiple
>> artifacts from the same module. In most cases, the end result is
>> broken and hard to use. The pom file that is published for a given
>> module is not able to describe correctly all artifacts of the module
>> and that's why there is one main artifact for every module; dependency
>> declarations are usually correct for the main artifact but are not
>> representative for the rest.
>>
>> For example, end-users who consume the hive-exec-core module tend to
>> think that maven will automatically resolve all transitive
>> dependencies and things will work as usual which is not the case. In
>> the past, this kind of assumption created a lot of confusion on
>> consumers of the hive-core-exec.jar with tickets and open debates that
>> spanned for multiple months. The discussions even reached a point
>> where people requested certain features of Hive to be reverted in
>> order to rectify some things around transitive dependencies and the
>> core jar.
>>
>> I think we should stick to the usual maven convention and just publish
>> one artifact for each module. Adding back and claiming to support the
>> "core" jar is a step backwards that just postpones the real problems
>> that we need to tackle.
>>
>> Furthermore, I don't think that the hive-exec module was ever meant to
>> be used as a dependency. This is mainly an application module and not
>> a library module and that's why shading takes place. Clearly some
>> parts from hive-exec could be considered to become a library and that
>> would be a promising direction going forward (splitting hive-exec into
>> other modules) but a bit outside the scope of the current discussion.
>>
>> From the issues outlined above the only actionable item that I see
>> concerns the joda library so we could try to simply relocate it if it
>> is causing issues.
>>
>> Finally, if someone wants to create a jar with specific contents from
>> the hive-exec module it is rather easy to do 

Re: Query Regarding Core Classified Hive-Exec Artifact in Future Releases

[Ayush Saxena]

Hi Mergu,
There are some reservations as of now, we are discussing that in another
thread. In the meantime, you can explore something as in [1]

-Ayush

[1] https://github.com/zabetak/hive-core-poc

On Mon, 22 Apr 2024 at 11:07, Mergu Ravi
 wrote:

> Hi Team,
> Is there any plan to include core classified HIve-exec artifacts in future
> releases?
>
> On Wed, Apr 17, 2024 at 1:09 PM Mergu Ravi <
> mergu.r...@gaianconsultants.com> wrote:
>
>> Hi Hive Team,
>> From this Hive ticket https://issues.apache.org/jira/browse/HIVE-25531,
>> I understood that the core classified hive-exec artifact was removed. Is
>> there any plan to include this core artifact in upcoming releases?
>> --
>>
>> Thanks & Regards,
>> Ravi Mergu
>>
>
>
> --
>
> 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: [Discussion] HIVE-28211: Restore hive-exec:core jar

[Ayush Saxena]

Stamatis,
Isn't the removal itself an incompatible change? There are a lot of
projects using it & we suddenly removed a jar because there were some
people not sure how to properly use it and were complaining about it.

What about the projects which are now stuck? reading the thread at [1],
there were promises made that everything will be relocated and sorted
before the release, but we couldn't, AFAIK it isn't a naive task to just
relocate all the dependencies.

As I see here @Chao Sun , even raised concerns [2], that the removal just
stops the way for upgrading downstream projects and it got countered like
folks chasing the removal will help chase getting all the dependencies
relocated or solve the issues for downstream. I think none volunteered.

I would either recommend:
* Best case we relocate all the dependencies present in hive-exec, not just
one or two. Somebody volunteers to raise one PR relocating "all" and we can
commit that and we should be sorted.
* Restore back the core jar, because a lot of projects depend on it, the
removal itself was incompatible, the removal I don't think had a clear
community agreement, it was a conditional agreement, which I don't think
got sorted, so we should rollback.

On a lighter note, we might release with some 5000+ commits, with best
performance or so, but if nobody is able to consume those release bits, I
think those efforts are just getting waste, eventually people will just
stick to their older versions and not even try to upgrade & we will be
releasing for nobody or maybe for few folks who just have only Hive in
their stack (I don't know if there are folks like that), No matter how good
a product is, if people don't use it, it is gonna die :-(


I think we have a ticket which talks about relocating all dependencies, I
agree we should drop the core jar for sure, it leads to all the problems as
Stamatis mentioned but lets restore the core jar back & we can drop it when
that relocation ticket is resolved. Does that sound convincing, or even
worth a thought?

btw. having jars with a set of dependencies shaded and other ones unshaded
is done in hadoop as well, hadoop-minicluster vs hadoop-client-minicluster
& such problems by users keep on coming, eg [3]

Anyone else, any thoughts?

-Ayush

[1] https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg
[2] https://lists.apache.org/thread/23sshgolmbpcc01npqgt03woljdy6hdn
[3] https://lists.apache.org/thread/f47s6bxrtslkxbc8s2gybwrxps8vk63x



On Fri, 26 Apr 2024 at 16:37, Stamatis Zampetakis  wrote:

> Hey Simhadri, thanks for starting this discussion.
>
> Maven has many limitations when it comes to publishing multiple
> artifacts from the same module. In most cases, the end result is
> broken and hard to use. The pom file that is published for a given
> module is not able to describe correctly all artifacts of the module
> and that's why there is one main artifact for every module; dependency
> declarations are usually correct for the main artifact but are not
> representative for the rest.
>
> For example, end-users who consume the hive-exec-core module tend to
> think that maven will automatically resolve all transitive
> dependencies and things will work as usual which is not the case. In
> the past, this kind of assumption created a lot of confusion on
> consumers of the hive-core-exec.jar with tickets and open debates that
> spanned for multiple months. The discussions even reached a point
> where people requested certain features of Hive to be reverted in
> order to rectify some things around transitive dependencies and the
> core jar.
>
> I think we should stick to the usual maven convention and just publish
> one artifact for each module. Adding back and claiming to support the
> "core" jar is a step backwards that just postpones the real problems
> that we need to tackle.
>
> Furthermore, I don't think that the hive-exec module was ever meant to
> be used as a dependency. This is mainly an application module and not
> a library module and that's why shading takes place. Clearly some
> parts from hive-exec could be considered to become a library and that
> would be a promising direction going forward (splitting hive-exec into
> other modules) but a bit outside the scope of the current discussion.
>
> From the issues outlined above the only actionable item that I see
> concerns the joda library so we could try to simply relocate it if it
> is causing issues.
>
> Finally, if someone wants to create a jar with specific contents from
> the hive-exec module it is rather easy to do so. I created a small POC
> project [1] on how someone can create something similar to the
> hive-exec-core.jar and incorporate it in their build. Each project has
> separate needs so for such customization I feel that the burden
> shouldn't fall on the Hive community.
>
> Best,
> Stamatis
>
> [1] https://github.com/zabetak/hive-core-poc
>
> On Thu, Apr 25, 2024 at 11:12 AM Simhadri G  wrote:
> >
> > Hi Everyone,
> >
> > The 

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

[Stamatis Zampetakis]

Hey Simhadri, thanks for starting this discussion.

Maven has many limitations when it comes to publishing multiple
artifacts from the same module. In most cases, the end result is
broken and hard to use. The pom file that is published for a given
module is not able to describe correctly all artifacts of the module
and that's why there is one main artifact for every module; dependency
declarations are usually correct for the main artifact but are not
representative for the rest.

For example, end-users who consume the hive-exec-core module tend to
think that maven will automatically resolve all transitive
dependencies and things will work as usual which is not the case. In
the past, this kind of assumption created a lot of confusion on
consumers of the hive-core-exec.jar with tickets and open debates that
spanned for multiple months. The discussions even reached a point
where people requested certain features of Hive to be reverted in
order to rectify some things around transitive dependencies and the
core jar.

I think we should stick to the usual maven convention and just publish
one artifact for each module. Adding back and claiming to support the
"core" jar is a step backwards that just postpones the real problems
that we need to tackle.

Furthermore, I don't think that the hive-exec module was ever meant to
be used as a dependency. This is mainly an application module and not
a library module and that's why shading takes place. Clearly some
parts from hive-exec could be considered to become a library and that
would be a promising direction going forward (splitting hive-exec into
other modules) but a bit outside the scope of the current discussion.

>From the issues outlined above the only actionable item that I see
concerns the joda library so we could try to simply relocate it if it
is causing issues.

Finally, if someone wants to create a jar with specific contents from
the hive-exec module it is rather easy to do so. I created a small POC
project [1] on how someone can create something similar to the
hive-exec-core.jar and incorporate it in their build. Each project has
separate needs so for such customization I feel that the burden
shouldn't fall on the Hive community.

Best,
Stamatis

[1] https://github.com/zabetak/hive-core-poc

On Thu, Apr 25, 2024 at 11:12 AM Simhadri G  wrote:
>
> Hi Everyone,
>
> The hive-exec:core jar is used by spark, oozie, hudi and many other projects. 
> Removal of the hive-exec:core jar has caused the following issues.
>
> Spark : https://lists.apache.org/list?dev@hive.apache.org:lte=1M:joda
> Oozie: https://lists.apache.org/thread/yld75ltf9y8d9q3cow3xqlg0fqyj6mkg
> Hudi: apache/hudi#8147
> Apache IotDB: https://lists.apache.org/thread/wdqsyj89w9cvyk1pyxr83hlxpg6zp1go
> Guava: https://github.com/google/guava/issues/
> joda-time: https://lists.apache.org/thread/sphgcvod3qx9wtc51ltpfyr8dpx9p294
>
> I understand that there is prior discussion about why the hive-exec:core jar 
> was removed here:
> https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg
>
> We agreed that ultimately hive-exec jar should be used over hive-exec:core 
> but there are quite a few dependencies that need to be shaded and relocated 
> for this.  https://issues.apache.org/jira/browse/HIVE-26220 .
>
> Until we shade & relocate dependencies in hive-exec, we should restore the 
> hive-exec:core jar . The intention for this is to provide a smoother 
> transition from the hive-exec:core to hive-exec jar for projects that depend 
> on hive .
>
> Seeking inputs from the community  and a way to move forward on this topic.
>
> I apologize in advance if I have missed anything.
>
> Thanks!
>
> Simhadri G

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

[Simhadri G]

Hi Everyone,

The hive-exec:core jar is used by spark, oozie, hudi and many other
projects. Removal of the hive-exec:core jar has caused the following issues.

   - Spark : https://lists.apache.org/list?dev@hive.apache.org:lte=1M:joda
   - Oozie: https://lists.apache.org/thread/yld75ltf9y8d9q3cow3xqlg0fqyj6mkg
   - Hudi: apache/hudi#8147 
   - Apache IotDB:
https://lists.apache.org/thread/wdqsyj89w9cvyk1pyxr83hlxpg6zp1go

   - Guava: https://github.com/google/guava/issues/
   - joda-time:
   https://lists.apache.org/thread/sphgcvod3qx9wtc51ltpfyr8dpx9p294

I understand that there is prior discussion about why the hive-exec:core
jar was removed here:
https://lists.apache.org/thread/cwtxnffoqpwgmdtlc9hyor2cm22djpkg

We agreed that ultimately hive-exec jar should be used over hive-exec:core
but there are quite a few dependencies that need to be shaded and relocated
for this.  https://issues.apache.org/jira/browse/HIVE-26220 .

Until we shade & relocate dependencies in hive-exec, we should restore the
hive-exec:core jar . The intention for this is to provide a smoother
transition from the hive-exec:core to hive-exec jar for projects that
depend on hive .

Seeking inputs from the community  and a way to move forward on this topic.

I apologize in advance if I have missed anything.

Thanks!

Simhadri G

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Chao Sun]

Thanks Cheng, I'll take a look at HIVE-28121 and create another RC.

> The vote email seems to have a wrong repository link, 1106. IIUC, 1128 is
the valid one, isn't it?

Oops. Yes it should be 1128. I reused the email content from my previous
release but forgot to change the link. Sorry about that.

Chao

On Wed, Apr 24, 2024 at 9:08 AM Dongjoon Hyun  wrote:

> Hi, Chao.
>
> The vote email seems to have a wrong repository link, 1106. IIUC, 1128 is
> the valid one, isn't it?
>
> Dongjoon.
>
> On 2024/04/20 20:01:53 Chao Sun wrote:
> > Apache Hive 2.3.10 Release Candidate 0 is available here:
> > https://people.apache.org/~sunchao/apache-hive-2.3.10-rc-0/
> > Maven artifacts are available here:
> > https://repository.apache.org/content/repositories/orgapachehive-1128
> >  >The
> > tag release-2.3.10-rc0 has been applied to the source for this
> > release in github, you can see it at
> > https://github.com/apache/hive/tree/release-2.3.10-rc0
> > Voting will conclude in 72 hours (or whenever I scrounge together enough
> > votes).
> >
> > Hive PMC Members: Please test and vote.
> >
> > Thanks.
> >
>

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Dongjoon Hyun]

Hi, Chao.

The vote email seems to have a wrong repository link, 1106. IIUC, 1128 is the 
valid one, isn't it?

Dongjoon.

On 2024/04/20 20:01:53 Chao Sun wrote:
> Apache Hive 2.3.10 Release Candidate 0 is available here:
> https://people.apache.org/~sunchao/apache-hive-2.3.10-rc-0/
> Maven artifacts are available here:
> https://repository.apache.org/content/repositories/orgapachehive-1128
> The
> tag release-2.3.10-rc0 has been applied to the source for this
> release in github, you can see it at
> https://github.com/apache/hive/tree/release-2.3.10-rc0
> Voting will conclude in 72 hours (or whenever I scrounge together enough
> votes).
> 
> Hive PMC Members: Please test and vote.
> 
> Thanks.
> 

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Cheng Pan]

Hi Stamatis,

HIVE-26882 got in 2.3.10, while a correctness issue was identified recently, 
HIVE-28121 fixes that.

I highly suggest including such a correctness patch in the final release of 2.3 
serials.

Thanks,
Cheng Pan

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Stamatis Zampetakis]

Hello,

I am not sure how to interpret the comments about HIVE-28121. Are we
waiting for HIVE-28121 to be merged for 2.3.10 or this release can
proceed even without it?

Best,
Stamatis

On Mon, Apr 22, 2024 at 10:37 AM Cheng Pan  wrote:
>
> I made integration tests with Apache Spark[1] and Apache Kyuubi[2], and 
> everything looks good so far.
>
> We may need to wait for HIVE-28121(affects HMS)[3] and prepare for the next 
> RC.
>
> Thanks to Chao for your efforts in making this release.
>
> [1] https://github.com/apache/spark/pull/45372
> [2] https://github.com/apache/kyuubi/pull/6328
> [3] https://github.com/apache/hive/pull/5204
>
> Thanks,
> Cheng Pan
>
>

Re: [VOTE] Apache Hive 2.3.10 Release Candidate 0

[Cheng Pan]

I made integration tests with Apache Spark[1] and Apache Kyuubi[2], and 
everything looks good so far.

We may need to wait for HIVE-28121(affects HMS)[3] and prepare for the next RC. 

Thanks to Chao for your efforts in making this release.

[1] https://github.com/apache/spark/pull/45372
[2] https://github.com/apache/kyuubi/pull/6328
[3] https://github.com/apache/hive/pull/5204

Thanks,
Cheng Pan

Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Kirti Ruge]

Congratulations Simhadri!!!

> On 20-Apr-2024, at 11:36 AM, Akshat m  wrote:
> 
> Congratulations Simhadri!, very well deserved 
> 
> On Fri, Apr 19, 2024 at 3:37 PM Simhadri G  > wrote:
> Thanks again everyone :) 
> 
> On Fri, Apr 19, 2024, 2:15 AM Rajesh Balamohan  > wrote:
> Congratulations Simhadri. :)
> 
> ~Rajesh.B
> 
> On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  > wrote:
> Congrats Simhadri ! 
> 
> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam  
> wrote:
> Congrats Simhadri. Looking forward to many more contributions in the future.
> 
> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala 
>  wrote:
> Congratulations Simhadri  well deserved
> 
> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  > wrote:
> Congratulations
> 
> Missatge de Alessandro Solimando  > del dia dj., 18 d’abr. 2024 a les 
> 17:40:
> 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 mailto:butaozha...@163.com>> 
> Sent: Thursday, April 18, 2024 5:39 PM
> To: u...@hive.apache.org ; dev 
> mailto:dev@hive.apache.org>>
> 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 
>  
>  > 代表 Ayush 
> Saxena mailto:ayush...@gmail.com>>
> 发送时间: 星期四, 四月 18, 2024 7:50 下午
> 收件人: dev mailto:dev@hive.apache.org>>; 
> u...@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)
> 
> 
> 
> -- 
> --
> Pau Tallada Crespí
> Departament de Serveis
> Port d'Informació Científica (PIC)
> Tel: +34 93 170 2729
> --
> 

Re: Query Regarding Core Classified Hive-Exec Artifact in Future Releases

[Mergu Ravi]

Hi Team,
Is there any plan to include core classified HIve-exec artifacts in future
releases?

On Wed, Apr 17, 2024 at 1:09 PM Mergu Ravi 
wrote:

> Hi Hive Team,
> From this Hive ticket https://issues.apache.org/jira/browse/HIVE-25531, I
> understood that the core classified hive-exec artifact was removed. Is
> there any plan to include this core artifact in upcoming releases?
> --
>
> Thanks & Regards,
> Ravi Mergu
>


-- 

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: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x

[Chao Sun]

Hi Cheng,

Sorry for the long delay. I was distracted by other things.

I just created RC0 for the Hive 2.3.10 release, and started a vote thread.
Please help to test if it looks good, especially from Spark side. Thanks!

Best,
Chao



On Thu, Apr 18, 2024 at 5:15 AM Cheng Pan  wrote:

> Hi Chao,
>
> The Spark community is starting to discuss the 4.0 release[1], can we make
> the Hive 2.3.10 release happen soon?
>
> [1] https://lists.apache.org/thread/nxmvz2j7kp96otzlnl3kd277knlb6qgb
>
> Thanks,
> Cheng Pan
>
> On 2024/01/17 17:50:37 Chao Sun wrote:
> > Hi Ayush,
> >
> > I'm working on the last few commits to backport to the branch.
> > Hopefully within 1-2 months I can start the release process. Our goal
> > is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this
> > year.
> >
> > Chao
> >
> > On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena  wrote:
> > >
> > > Thanx everyone for the feedback, I have started a formal thread to
> mark 1.x
> > > EOL. We can have one last release for 2.x as Chao mentioned, with some
> > > required changes + our CVE's & get the release line marked as EOL then.
> > >
> > > @Chao Sun  Do let us know if you have a proposed
> > > timeline for that.
> > >
> > > -Ayush
> > >
> > > On Wed, 17 Jan 2024 at 08:23, vihang karajgaonkar 
> > > wrote:
> > >
> > > > I was confused about the subject line since it says 3.x as well
> along with
> > > > 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or
> just 1.x
> > > > and 2.x?
> > > >
> > > > I think it makes sense to EOL 1.x. Looks like 2.x is still being
> maintained
> > > > by Chao and I think we were backporting PRs to the 3.x line pretty
> recently
> > > > so I believe we should wait out for a release on Hive 3.x.
> > > >
> > > > Thanks,
> > > > Vihang
> > > >
> > > > On Tue, Jan 16, 2024 at 3:40 PM Attila Turoczy
> > > >  wrote:
> > > >
> > > > > Dear PMC's,
> > > > >
> > > > > Do we have a verdict / decision about this?
> > > > >
> > > > > -Attila
> > > > >
> > > > > On Wed, Jan 10, 2024 at 5:45 PM Chao Sun  wrote:
> > > > >
> > > > > > On Hive 2.x, I'm still preparing for another release 2.3.10
> (Hive 2.3
> > > > > > branch is being actively maintained so far). Hopefully this will
> be
> > > > > > the last release in the branch-2 line.
> > > > > >
> > > > > > +1 on making Hive 1 EOL for the time being.
> > > > > >
> > > > > > Chao
> > > > > >
> > > > > > On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan
> > > > > >  wrote:
> > > > > > >
> > > > > > > +1 for making both Hive 1&2 EOL
> > > > > > >
> > > > > > > -Sankar
> > > > > > > -Original Message-
> > > > > > > From: Attila Turoczy 
> > > > > > > Sent: Wednesday, January 10, 2024 7:37 PM
> > > > > > > To: dev@hive.apache.org
> > > > > > > Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x,
> 2.x, 3.x
> > > > > > >
> > > > > > > [You don't often get email from aturo...@cloudera.com.invalid.
> Learn
> > > > > > why this is important at
> https://aka.ms/LearnAboutSenderIdentification
> > > > ]
> > > > > > >
> > > > > > > +1 for making it EOL for Hive 1 and Hive 2. I do not think
> these 2
> > > > > > product
> > > > > > > branches are relevant in 2023.
> > > > > > >
> > > > > > > -Attila
> > > > > > >
> > > > > > > On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko <
> > > > dkuzme...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +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
> > > > > > > >
> > > > > >
> > > > >
> > > >
> >
>
>
>
>

[VOTE] Apache Hive 2.3.10 Release Candidate 0

[Chao Sun]

Apache Hive 2.3.10 Release Candidate 0 is available here:
https://people.apache.org/~sunchao/apache-hive-2.3.10-rc-0/
Maven artifacts are available here:
https://repository.apache.org/content/repositories/orgapachehive-1128
The
tag release-2.3.10-rc0 has been applied to the source for this
release in github, you can see it at
https://github.com/apache/hive/tree/release-2.3.10-rc0
Voting will conclude in 72 hours (or whenever I scrounge together enough
votes).

Hive PMC Members: Please test and vote.

Thanks.

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

[Akshat m]

Congratulations Simhadri!, very well deserved

On Fri, Apr 19, 2024 at 3:37 PM Simhadri G  wrote:

> Thanks again everyone :)
>
> On Fri, Apr 19, 2024, 2:15 AM Rajesh Balamohan 
> wrote:
>
>> Congratulations Simhadri. :)
>>
>> ~Rajesh.B
>>
>> On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  wrote:
>>
>>> Congrats Simhadri !
>>>
>>> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam
>>>  wrote:
>>>
 Congrats Simhadri. Looking forward to many more contributions in the
 future.

 On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
  wrote:

> Congratulations Simhadri  well deserved
>
> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>
>> Congratulations
>>
>> Missatge de Alessandro Solimando 
>> del dia dj., 18 d’abr. 2024 a les 17:40:
>>
>>> 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:* u...@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 
> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
> *收件人**:* dev ; u...@hive.apache.org <
> u...@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)
>

>>
>> --
>> --
>> Pau Tallada Crespí
>> Departament de Serveis
>> Port d'Informació Científica (PIC)
>> Tel: +34 93 170 2729
>> --
>>
>>

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

[Simhadri G]

Thanks again everyone :)

On Fri, Apr 19, 2024, 2:15 AM Rajesh Balamohan 
wrote:

> Congratulations Simhadri. :)
>
> ~Rajesh.B
>
> On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  wrote:
>
>> Congrats Simhadri !
>>
>> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam
>>  wrote:
>>
>>> Congrats Simhadri. Looking forward to many more contributions in the
>>> future.
>>>
>>> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
>>>  wrote:
>>>
 Congratulations Simhadri  well deserved

 On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:

> Congratulations
>
> Missatge de Alessandro Solimando  del
> dia dj., 18 d’abr. 2024 a les 17:40:
>
>> 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:* u...@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 
 *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
 *收件人**:* dev ; u...@hive.apache.org <
 u...@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)

>>>
>
> --
> --
> Pau Tallada Crespí
> Departament de Serveis
> Port d'Informació Científica (PIC)
> Tel: +34 93 170 2729
> --
>
>

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

[Rajesh Balamohan]

Congratulations Simhadri. :)

~Rajesh.B

On Fri, Apr 19, 2024 at 2:02 AM Aman Sinha  wrote:

> Congrats Simhadri !
>
> On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam
>  wrote:
>
>> Congrats Simhadri. Looking forward to many more contributions in the
>> future.
>>
>> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
>>  wrote:
>>
>>> Congratulations Simhadri  well deserved
>>>
>>> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>>>
 Congratulations

 Missatge de Alessandro Solimando  del
 dia dj., 18 d’abr. 2024 a les 17:40:

> 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:* u...@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 
>>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>>> *收件人**:* dev ; u...@hive.apache.org <
>>> u...@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)
>>>
>>

 --
 --
 Pau Tallada Crespí
 Departament de Serveis
 Port d'Informació Científica (PIC)
 Tel: +34 93 170 2729
 --

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

[Aman Sinha]

Congrats Simhadri !

On Thu, Apr 18, 2024 at 12:25 PM Naveen Gangam 
wrote:

> Congrats Simhadri. Looking forward to many more contributions in the
> future.
>
> On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
>  wrote:
>
>> Congratulations Simhadri  well deserved
>>
>> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>>
>>> Congratulations
>>>
>>> Missatge de Alessandro Solimando  del
>>> dia dj., 18 d’abr. 2024 a les 17:40:
>>>
 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:* u...@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 
>> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
>> *收件人**:* dev ; u...@hive.apache.org <
>> u...@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)
>>
>
>>>
>>> --
>>> --
>>> Pau Tallada Crespí
>>> Departament de Serveis
>>> Port d'Informació Científica (PIC)
>>> Tel: +34 93 170 2729
>>> --
>>>
>>>

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

[Naveen Gangam]

Congrats Simhadri. Looking forward to many more contributions in the future.

On Thu, Apr 18, 2024 at 12:25 PM Sai Hemanth Gantasala
 wrote:

> Congratulations Simhadri  well deserved
>
> On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:
>
>> Congratulations
>>
>> Missatge de Alessandro Solimando  del
>> dia dj., 18 d’abr. 2024 a les 17:40:
>>
>>> 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:* u...@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 
> *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
> *收件人**:* dev ; u...@hive.apache.org <
> u...@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)
>

>>
>> --
>> --
>> Pau Tallada Crespí
>> Departament de Serveis
>> Port d'Informació Científica (PIC)
>> Tel: +34 93 170 2729
>> --
>>
>>

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

[Sai Hemanth Gantasala]

Congratulations Simhadri  well deserved

On Thu, Apr 18, 2024 at 8:41 AM Pau Tallada  wrote:

> Congratulations
>
> Missatge de Alessandro Solimando  del dia
> dj., 18 d’abr. 2024 a les 17:40:
>
>> 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:* u...@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
 
 *发送时间**:* 星期四, 四月 18, 2024 7:50 下午
 *收件人**:* dev ; u...@hive.apache.org <
 u...@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)

>>>
>
> --
> --
> Pau Tallada Crespí
> Departament de Serveis
> Port d'Informació Científica (PIC)
> Tel: +34 93 170 2729
> --
>
>

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:* u...@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 ; u...@hive.apache.org <
>> u...@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: [ANNOUNCE] New Committer: Simhadri Govindappa

[Krisztian Kasa]

Congratulations Simhadri!

Regards,
Krisztian

On Thu, Apr 18, 2024 at 3:25 PM kokila narayanan <
kokilanarayana...@gmail.com> wrote:

> Congratulations Simhadri 
>
> On Thu, 18 Apr, 2024, 17:22 Ayush Saxena,  wrote:
>
>> 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: [ANNOUNCE] New Committer: Simhadri Govindappa

[kokila narayanan]

Congratulations Simhadri 

On Thu, 18 Apr, 2024, 17:22 Ayush Saxena,  wrote:

> 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: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Simhadri G]

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:* u...@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 ; u...@hive.apache.org <
> u...@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: Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Sankar Hariappan]

Congrats Simhadri!

-Sankar

From: Butao Zhang 
Sent: Thursday, April 18, 2024 5:39 PM
To: u...@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
 
mailto:user-return-28075-butaozhang1=163@hive.apache.org>>
 代表 Ayush Saxena mailto:ayush...@gmail.com>>
发送时间: 星期四, 四月 18, 2024 7:50 下午
收件人: dev mailto:dev@hive.apache.org>>; 
u...@hive.apache.org 
mailto:u...@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: [DISCUS] Plan the next Hive release

[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: Issue with joda-time library bundled in hive-exec:4.0.0

[Cheng Pan]

Simhadri, thank you for sharing the information.

Thanks,
Cheng Pan

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

[Cheng Pan]

Hi Chao,

The Spark community is starting to discuss the 4.0 release[1], can we make the 
Hive 2.3.10 release happen soon?

[1] https://lists.apache.org/thread/nxmvz2j7kp96otzlnl3kd277knlb6qgb

Thanks,
Cheng Pan

On 2024/01/17 17:50:37 Chao Sun wrote:
> Hi Ayush,
> 
> I'm working on the last few commits to backport to the branch.
> Hopefully within 1-2 months I can start the release process. Our goal
> is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this
> year.
> 
> Chao
> 
> On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena  wrote:
> >
> > Thanx everyone for the feedback, I have started a formal thread to mark 1.x
> > EOL. We can have one last release for 2.x as Chao mentioned, with some
> > required changes + our CVE's & get the release line marked as EOL then.
> >
> > @Chao Sun  Do let us know if you have a proposed
> > timeline for that.
> >
> > -Ayush
> >
> > On Wed, 17 Jan 2024 at 08:23, vihang karajgaonkar 
> > wrote:
> >
> > > I was confused about the subject line since it says 3.x as well along with
> > > 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or just 1.x
> > > and 2.x?
> > >
> > > I think it makes sense to EOL 1.x. Looks like 2.x is still being 
> > > maintained
> > > by Chao and I think we were backporting PRs to the 3.x line pretty 
> > > recently
> > > so I believe we should wait out for a release on Hive 3.x.
> > >
> > > Thanks,
> > > Vihang
> > >
> > > On Tue, Jan 16, 2024 at 3:40 PM Attila Turoczy
> > >  wrote:
> > >
> > > > Dear PMC's,
> > > >
> > > > Do we have a verdict / decision about this?
> > > >
> > > > -Attila
> > > >
> > > > On Wed, Jan 10, 2024 at 5:45 PM Chao Sun  wrote:
> > > >
> > > > > On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive 2.3
> > > > > branch is being actively maintained so far). Hopefully this will be
> > > > > the last release in the branch-2 line.
> > > > >
> > > > > +1 on making Hive 1 EOL for the time being.
> > > > >
> > > > > Chao
> > > > >
> > > > > On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan
> > > > >  wrote:
> > > > > >
> > > > > > +1 for making both Hive 1&2 EOL
> > > > > >
> > > > > > -Sankar
> > > > > > -Original Message-
> > > > > > From: Attila Turoczy 
> > > > > > Sent: Wednesday, January 10, 2024 7:37 PM
> > > > > > To: dev@hive.apache.org
> > > > > > Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, 3.x
> > > > > >
> > > > > > [You don't often get email from aturo...@cloudera.com.invalid. Learn
> > > > > why this is important at https://aka.ms/LearnAboutSenderIdentification
> > > ]
> > > > > >
> > > > > > +1 for making it EOL for Hive 1 and Hive 2. I do not think these 2
> > > > > product
> > > > > > branches are relevant in 2023.
> > > > > >
> > > > > > -Attila
> > > > > >
> > > > > > On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko <
> > > dkuzme...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 for marking Hive 1.x EOL
> > > > > > >
> > > > > > > Assuming no volunteers willing to take ownership of branch-2
> > > > > maintenance,
> > > > > > > +1 to declare it EOL as well.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Denys
> > > > > > >
> > > > >
> > > >
> > >
>  

Re: [ANNOUNCE] New Committer: Simhadri Govindappa

[Butao Zhang]

  
  
  

Congratulations Simhadri !!!
Thanks.
  

 发件人: user-return-28075-butaozhang1=163@hive.apache.org  代表 Ayush Saxena 发送时间: 星期四, 四月 18, 2024 7:50 下午收件人: dev ; u...@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)

[ANNOUNCE] New Committer: Simhadri Govindappa

[Ayush Saxena]

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: [DISCUS] Plan the next Hive release

[Stamatis Zampetakis]

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: [Blog] Apache Hive 4.0 Release blog for ASF M & P

[Ayush Saxena]

Update:
I submitted this last week, and I circled back to check, this is being
reviewed and they are dropping, tweaking a couple of things and writing
some Apache stuff & all to follow their template(Which I should have done
myself, they shared the template of Apache Wicket), those things we don’t
have any control over. M folks will take care of it. So, it will look a
bit different then what we submitted.

I have been communicated that:* It is supposed to be published before end
of month*

PS. They asked for some quotes for the release, which I have said I don’t
have. We can drop adding that, either they will drop or add from their own.
But I think they will write something themselves

I think it will be finalized soon, I will keep the thread updated as I get
anything or If I find it got published itself :-)

-Ayush


On 5 Apr 2024, at 5:39 PM, Ayush Saxena  wrote:


Hi Stamatis,
I have changed the permissions to allow everyone with the link to have
comment access. I have additionally given you edit access as well.

Let me know if things don't work

-Ayush

On Fri, 5 Apr 2024 at 17:34, Stamatis Zampetakis  wrote:

> Great initiative and nice content. Overall, it looks great!
>
> I have some minor comments. Is it possible to change permissions allow
> comments from anyone or it has to be done on a per user basis?
>
> Best,
> Stamatis
>
> On Fri, Apr 5, 2024 at 1:54 PM Ayush Saxena  wrote:
> >
> > Hi All,
> >
> > Have been talking to the ASF M & P team and they recongonise the 4.0
> release is a big milestone for our project.
> >
> > They are happy to have an entry for us in the their news column, ex:
> >
> https://news.apache.org/foundation/entry/apache-software-foundation-announces-apache-wicket-v10
> >
> > So, I along with Denys, Simhadri & tons of help from ChatGpt have
> prepared a draft to share with them.
> > The draft is here:
> >
> >
> https://docs.google.com/document/d/10Zu8pHvWNDRTqn7yvYqvU4-kw3Q1TXo7mGo5m5fUP2Y/edit
> >
> > If you have some feedback or concerns, please share with us.
> >
> > If you want some improvements or removals, let us know here & we will do
> that, or if you need write access to this page, just let me know.
> >
> > If nobody objects, I plan to send this to the team by next week Tuesday
> >
> >
> > -Ayush
>

Re: [DISCUS] Plan the next Hive release

[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: [DISCUS] Plan the next Hive release

[Stamatis Zampetakis]

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

[Simhadri G]

Hi Cheng Pan,

There is long running Hive mail thread discussing this here:
https://lists.apache.org/thread/sxcrcf4v9j630tl9domp0bn4m33bdq0s


On Thu, Apr 18, 2024 at 11:15 AM Cheng Pan  wrote:

> Hi Ayush,
>
> > Hive is already in discussion of marking Hive-2.x EOL, so at very best
> we would have one release and immediately after that we will announce it EOL
>
> Does the discussion happen in public? Is there an ETA for the final
> release of branch-2.3?
>
> Thanks,
> Cheng Pan
>
>
> > On Apr 17, 2024, at 18:03, Ayush Saxena  wrote:
> >
> > Thanx Cheng Pan for sharing the pointers, Do you have any list of issues
> or pointers on what are the challenges for Spark to move to a higher Hive
> version? I know upgrading libraries is quite challenging but it is
> inevitable.
> >
> > Hive is already in discussion of marking Hive-2.x EOL, so at very best
> we would have one release and immediately after that we will announce it
> EOL, maintaining a release line is quite an effort for us at Hive & doing
> it because other projects doesn't want to upgrade isn't a convincing reason
> for most of us. The best we can do is or are trying is to address issues
> for Spark whatever we can do as part of Hive code & would definitely need
> help/support from Spark side as well, since the move is from 2.x to 4.x, it
> would be a big change and would offer resistance on both sides.
> >
> > So, it would be great help if any pointers can be shared from Spark side
> for the move, if there is no help/interest from Spark then we can't do
> anything & there is no need for Hive-2.x either in that case :-)
> >
> > -Ayush
> >
> > On Wed, 17 Apr 2024 at 15:00, Cheng Pan  wrote:
> > > … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our
> initial hunch is that it would be quite challenging without a hive-exec
> slim jar …
> >
> > It should be challenging to upgrade Spark’s built-in Hive version.
> Actually, we already did lots of work on branch-2.3 which focuses on CVE
> reduction, for example, allowing Spark to upgrade Guava to modern versions
> to get rid of Guava 14, it was tested with the latest Spark master
> branch[1], maybe we need a release for 2.3.10 now.
> >
> > [1] https://github.com/apache/spark/pull/45372
> >
> > Thanks,
> > Cheng Pan
> >
> >
>
>

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

[Cheng Pan]

Hi Ayush,

> Hive is already in discussion of marking Hive-2.x EOL, so at very best we 
> would have one release and immediately after that we will announce it EOL

Does the discussion happen in public? Is there an ETA for the final release of 
branch-2.3?

Thanks,
Cheng Pan


> On Apr 17, 2024, at 18:03, Ayush Saxena  wrote:
> 
> Thanx Cheng Pan for sharing the pointers, Do you have any list of issues or 
> pointers on what are the challenges for Spark to move to a higher Hive 
> version? I know upgrading libraries is quite challenging but it is inevitable.
> 
> Hive is already in discussion of marking Hive-2.x EOL, so at very best we 
> would have one release and immediately after that we will announce it EOL, 
> maintaining a release line is quite an effort for us at Hive & doing it 
> because other projects doesn't want to upgrade isn't a convincing reason for 
> most of us. The best we can do is or are trying is to address issues for 
> Spark whatever we can do as part of Hive code & would definitely need 
> help/support from Spark side as well, since the move is from 2.x to 4.x, it 
> would be a big change and would offer resistance on both sides.
> 
> So, it would be great help if any pointers can be shared from Spark side for 
> the move, if there is no help/interest from Spark then we can't do anything & 
> there is no need for Hive-2.x either in that case :-) 
> 
> -Ayush
> 
> On Wed, 17 Apr 2024 at 15:00, Cheng Pan  wrote:
> > … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our initial 
> > hunch is that it would be quite challenging without a hive-exec slim jar …
> 
> It should be challenging to upgrade Spark’s built-in Hive version. Actually, 
> we already did lots of work on branch-2.3 which focuses on CVE reduction, for 
> example, allowing Spark to upgrade Guava to modern versions to get rid of 
> Guava 14, it was tested with the latest Spark master branch[1], maybe we need 
> a release for 2.3.10 now.
> 
> [1] https://github.com/apache/spark/pull/45372
> 
> Thanks,
> Cheng Pan
> 
> 

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

[Ayush Saxena]

Thanx Cheng Pan for sharing the pointers, Do you have any list of issues or
pointers on what are the challenges for Spark to move to a higher Hive
version? I know upgrading libraries is quite challenging but it
is inevitable.

Hive is already in discussion of marking Hive-2.x EOL, so at very best we
would have one release and immediately after that we will announce it EOL,
maintaining a release line is quite an effort for us at Hive & doing it
because other projects doesn't want to upgrade isn't a convincing reason
for most of us. The best we can do is or are trying is to address issues
for Spark whatever we can do as part of Hive code & would definitely need
help/support from Spark side as well, since the move is from 2.x to 4.x, it
would be a big change and would offer resistance on both sides.

So, it would be great help if any pointers can be shared from Spark side
for the move, if there is no help/interest from Spark then we can't do
anything & there is no need for Hive-2.x either in that case :-)

-Ayush

On Wed, 17 Apr 2024 at 15:00, Cheng Pan  wrote:

> > … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our initial
> hunch is that it would be quite challenging without a hive-exec slim jar …
>
> It should be challenging to upgrade Spark’s built-in Hive version.
> Actually, we already did lots of work on branch-2.3 which focuses on CVE
> reduction, for example, allowing Spark to upgrade Guava to modern versions
> to get rid of Guava 14, it was tested with the latest Spark master
> branch[1], maybe we need a release for 2.3.10 now.
>
> [1] https://github.com/apache/spark/pull/45372
>
> Thanks,
> Cheng Pan
>
>
>

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

[Cheng Pan]

> … we are exploring ways to get Spark move from 2.3.9 to 4.0, Our initial 
> hunch is that it would be quite challenging without a hive-exec slim jar …

It should be challenging to upgrade Spark’s built-in Hive version. Actually, we 
already did lots of work on branch-2.3 which focuses on CVE reduction, for 
example, allowing Spark to upgrade Guava to modern versions to get rid of Guava 
14, it was tested with the latest Spark master branch[1], maybe we need a 
release for 2.3.10 now.

[1] https://github.com/apache/spark/pull/45372

Thanks,
Cheng Pan