[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-09 Thread Sergey Shelukhin (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393675#comment-16393675
 ] 

Sergey Shelukhin commented on TEZ-3900:
---

Nm, we actually just broke our own shading so tez jar came first on the 
classpath after that. I guess this can wait for TEZ-2164

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-08 Thread Jonathan Eagles (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391985#comment-16391985
 ] 

Jonathan Eagles commented on TEZ-3900:
--

http://tez.apache.org/install.html

- Prefer tez tarball tarball install to hdfs and specify subdirectory so that 
tez classpath is reliably after hive classpath. This avoids two versions of 
dependencies in the same directory which is not defined what order they are 
resolved in the classpath.
Example:
{noformat:title=tez-site.xml}
  
tez.lib.uris
${fs.defaultFS}/apps/tez-x.y.z/tez-x.y.z-minimal.tar.gz#tez
  
  
tez.lib.uris.classpath
./tez/*,./tez/lib/*
  
{noformat}
http://tez.apache.org/install.html

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-08 Thread Sergey Shelukhin (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391955#comment-16391955
 ] 

Sergey Shelukhin commented on TEZ-3900:
---

Where can one view the best practices? :)
We were deploying Guava 11 because of the dependency version in Tez, and are 
hitting issue in Hive due to lack of API compat (Hive is on 19). 
We are going to try deploying 19 for everything and see if it works.

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-07 Thread Jonathan Eagles (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390138#comment-16390138
 ] 

Jonathan Eagles commented on TEZ-3900:
--

If you are deploying tez according to best practices, then the guava version 
from hive should be used and not the one from tez. Can you describe the actual 
failure you see. Also, would you say the failure is intermittent or does it 
always fail.

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-07 Thread Sergey Shelukhin (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390121#comment-16390121
 ] 

Sergey Shelukhin commented on TEZ-3900:
---

Hmm... the problem we actually have is that Hive has recently upgraded guava 
and we are hitting issues due to the old version coming from Tez.
The referenced JIRA hasn't had any progress in almost 2 years, I wonder if it's 
time to just upgrade it and force Hive/Pig to upgrade too (Hive has already 
done that, in fact).

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-07 Thread Jonathan Eagles (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389767#comment-16389767
 ] 

Jonathan Eagles commented on TEZ-3900:
--

It is difficult to upgrade guava directly like this, which is why it hasn't 
been done yet. This will force all users of tez (pig/hive/etc) plus all users 
of that code to be forced to upgrade accordingly. Instead we have been taking 
an approach where Tez can easily switch between versions of guava (essentially 
using a subset of APIs that work across all supported versions of guava). To 
that point there is another jira that is taking a completely different approach 
to shade guava in tez and have users rely directly on library provided by 
pig/hive or possibly hadoop directly.

Please have a look at the reference jira TEZ-2164

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-06 Thread Eric Wohlstadter (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389039#comment-16389039
 ] 

Eric Wohlstadter commented on TEZ-3900:
---

[~sershe]

Tez is still defaulting to Hadoop 2.7.0.

I've tested Tez with Guava 19.0 on Hadoop 3.0.0, so there should be no problem 
there.

Do you think there is any reason Guava 19.0 would conflict with Hadoop 2.7.x, 
2.8.x?

If not, LGTM.

If it might cause conflicts, we can put Guava deps into version profiles, i.e. 
-Phadoop28, -Phadoop3, etc..

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (TEZ-3900) upgrade to a recent guava version

2018-03-06 Thread Sergey Shelukhin (JIRA)

[ 
https://issues.apache.org/jira/browse/TEZ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388901#comment-16388901
 ] 

Sergey Shelukhin commented on TEZ-3900:
---

[~ewohlstadter] [~hagleitn] can you take a look?

> upgrade to a recent guava version
> -
>
> Key: TEZ-3900
> URL: https://issues.apache.org/jira/browse/TEZ-3900
> Project: Apache Tez
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: TEZ-3900.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)