[jira] [Comment Edited] (HIVE-21961) Update jetty version to 9.4.x

2020-12-30 Thread Chao Sun (Jira) 


[ 
https://issues.apache.org/jira/browse/HIVE-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256699#comment-17256699
 ] 

Chao Sun edited comment on HIVE-21961 at 12/30/20, 8:07 PM:


HADOOP-16152 is also in Hadoop 3.1.4 so can we upgrade to that instead 
[~abstractdog]? it could be easier since Hive is now on Hadoop 3.1.0.


was (Author: csun):
HADOOP-16152 is also in Hadoop 3.1.4 so can we upgrade to that instead? it 
could be easier since Hive is now on Hadoop 3.1.0.

> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: László Bodor
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, 
> HIVE-21961.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Update jetty version to 9.4.x



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

[jira] [Comment Edited] (HIVE-21961) Update jetty version to 9.4.x

2020-02-21 Thread Jira 


[ 
https://issues.apache.org/jira/browse/HIVE-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17041694#comment-17041694
 ] 

László Bodor edited comment on HIVE-21961 at 2/21/20 9:12 AM:
--

created HIVE-22916 for blocking this
I think, having 2 different versions in jetty would be painful even in 
preCommit time (see test failures above), instead we should wait for hadoop 
3.2.2 (with jetty 9.4.x, see HADOOP-16152) to be released and move forward 
here, depending on that

important note that, since hadoop 3.2.1, it depends on guava27, but it's still 
on jetty 9.3...if we want to avoid endless pom.xml hacks and shading, we should 
move to hadoop 3.2.2, and upgrade jetty+guava at the same
cc: [~hashutosh]


was (Author: abstractdog):
created HIVE-22916 for blocking this
I think, having 2 different versions in jetty would be painful even in 
preCommit time (see test failures above), instead we should wait for hadoop 
3.2.2 (with jetty 9.4.x) to be released and move forward here, depending on that

important note that, since hadoop 3.2.1, it depends on guava27, but it's still 
on jetty 9.3...if we want to avoid endless pom.xml hacks and shading, we should 
move to hadoop 3.2.2, and upgrade jetty+guava at the same
cc: [~hashutosh]

> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: László Bodor
>Priority: Major
> Attachments: HIVE-21961.02.patch, HIVE-21961.03.patch, 
> HIVE-21961.patch
>
>
> Update jetty version to 9.4.x



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