Yes that would be a good idea

 You should just be able to change a single property and see if it Will 
compile. See the instructions on the website:

http://jena.apache.org/documentation/hadoop/artifacts.html

Rob

On 31/03/2017 13:57, "A. Soroka" <aj...@virginia.edu> wrote:

    So for next steps, should someone (aka me) try to build against a 3.X 
Hadoop to see where the jolts are? Does that make sense as a way to gather more 
info? I would just go ahead and do it, but lacking (as I do) any Hadoop dev 
experience, I want to make sure that it's a good idea before investing time.
    
    ---
    A. Soroka
    The University of Virginia Library
    
    > On Mar 31, 2017, at 5:11 AM, Rob Vesse <rve...@dotnetrdf.org> wrote:
    > 
    > My impression is that 3.0 is still a long way off a generally available 
release since they are still in Alpha at the moment.
    > 
    > I would expect that 2.x would remain the primary distribution for a while 
yet.
    > 
    > I don’t know how much, If at all, map/reduce has changed so it may 
already be possible to build Elephas against 3.X without any changes but then 
again it might not.
    > 
    > I’m not sure that it is necessarily safe to stop shading Guava. It is a 
widely used library with poor compatibility between versions and our users may 
experience Version conflicts in other environments.
    > 
    > Rob
    > 
    > On 29/03/2017 00:18, "Bruno P. Kinoshita" <ki...@apache.org> wrote:
    > 
    >> I would think we could go with a minor version for this, no? Or is 
    >    Elephas such a big part of our offering that we need to make a major 
    >    release to move with Hadoop...?
    > 
    > 
    >    I would think the same. Unless we have other important features to be 
released, maybe something that breaks backward compatibility, etc.
    > 
    > 
    > 
    >    ________________________________
    >    From: A. Soroka <aj...@virginia.edu>
    >    To: dev@jena.apache.org 
    >    Sent: Wednesday, 29 March 2017 3:20 AM
    >    Subject: Re: [jira] [Updated] (HADOOP-10101) Update guava dependency 
to the latest version
    > 
    > 
    > 
    >> * Jena would have to move in step with Hadoop and drop support for older 
versions.
    > 
    >    Maybe we can see what Hadoop itself ends up doing for this problem... 
they are targeting their own major release 3 for this. I would think we could 
go with a minor version for this, no? Or is Elephas such a big part of our 
offering that we need to make a major release to move with Hadoop...?
    > 
    >    ---
    >    A. Soroka
    >    The University of Virginia Library
    > 
    > 
    >> On Mar 25, 2017, at 7:15 AM, Andy Seaborne <a...@apache.org> wrote:
    >> 
    >> 
    >> Step 1: upgrade jena-shaded-guava to v21.0
    >> 
    >> and see if it works.
    >> 
    >> 
    >> There are at least two considerations:
    >> 
    >> * Jena would have to move in step with Hadoop
    >> and drop support for older versions.
    >> * Our downstream users may have guava version choices.
    >> 
    >> and we have to wait until a Hadoop release to remove it.
    >> 
    >>   Andy
    >> 
    >> On 25/03/17 01:22, A. Soroka wrote:
    >>> Looks like Hadoop has successfully updated their Guava dependency-- 
this might provide us the opportunity to stop shading Guava. (yay!)
    >>> 
    >>> ---
    >>> A. Soroka
    >>> The University of Virginia Library
    >>> 
    >>>> Begin forwarded message:
    >>>> 
    >>>> From: "Tsuyoshi Ozawa (JIRA)" <j...@apache.org>
    >>>> Subject: [jira] [Updated] (HADOOP-10101) Update guava dependency to 
the latest version
    >>>> Date: March 24, 2017 at 9:18:42 PM EDT
    >>>> To: aj...@apache.org
    >>>> 
    >>>> 
    >>>>   [ 
https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]
    >>>> 
    >>>> Tsuyoshi Ozawa updated HADOOP-10101:
    >>>> ------------------------------------
    >>>>     Resolution: Fixed
    >>>>  Fix Version/s: 3.0.0-alpha3
    >>>>         Status: Resolved  (was: Patch Available)
    >>>> 
    >>>> Committed this to trunk. Thanks Nicholas and Steve for your review, 
and thanks people who joined this issue for your comments.
    >>>> 
    >>>>> Update guava dependency to the latest version
    >>>>> ---------------------------------------------
    >>>>> 
    >>>>>              Key: HADOOP-10101
    >>>>>              URL: https://issues.apache.org/jira/browse/HADOOP-10101
    >>>>>          Project: Hadoop Common
    >>>>>       Issue Type: Improvement
    >>>>> Affects Versions: 3.0.0-alpha2
    >>>>>         Reporter: Rakesh R
    >>>>>         Assignee: Tsuyoshi Ozawa
    >>>>>           Labels: BB2015-05-TBR
    >>>>>          Fix For: 3.0.0-alpha3
    >>>>> 
    >>>>>      Attachments: HADOOP-10101-002.patch, HADOOP-10101-004.patch, 
HADOOP-10101-005.patch, HADOOP-10101-006.patch, HADOOP-10101-007.patch, 
HADOOP-10101-008.patch, HADOOP-10101-009.patch, HADOOP-10101-009.patch, 
HADOOP-10101-010.patch, HADOOP-10101-010.patch, HADOOP-10101-011.patch, 
HADOOP-10101.012.patch, HADOOP-10101.013.patch, HADOOP-10101.014.patch, 
HADOOP-10101.015.patch, HADOOP-10101.016.patch, HADOOP-10101.017.patch, 
HADOOP-10101.018.patch, HADOOP-10101.patch, HADOOP-10101.patch
    >>>>> 
    >>>>> 
    >>>>> The existing guava version is 11.0.2 which is quite old. This issue 
tries to update the version to as latest version as possible.
    >>>> 
    >>>> 
    >>>> 
    >>>> --
    >>>> This message was sent by Atlassian JIRA
    >>>> (v6.3.15#6346)
    >>> 
    > 
    > 
    > 
    > 
    > 
    
    




Reply via email to