accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: VFS version in 1.6.6 binary release
Date Fri, 02 Dec 2016 22:42:11 GMT
The backport may only be necessary if you are building Accumulo from
source. You may be able to drop in 2.1 as a replacement for 2.0 in the
classpath on the pre-built binaries, without a problem.

On Fri, Dec 2, 2016 at 1:00 PM Michael Wall <mjwall@gmail.com> wrote:

> Andrew,
>
> You should be fine upgrading commons-vfs to 2.1 with Accumulo 1.6.4.  Ran
> that way for a long time with no problems.
>
> Mike
>
> On Fri, Dec 2, 2016 at 12:57 PM, Andrew Hulbert <ahulbert@ccri.com> wrote:
>
> Thanks all. Thanks! Think it would be safe to upgrade the VFS then with
> 1.6.4 as well?
>
> Andrew
> On 12/02/2016 12:37 PM, Christopher wrote:
>
> The release notes for 1.6.6 are in error. I'll update them.
>
> On Fri, Dec 2, 2016 at 11:36 AM Michael Wall < <mjwall@gmail.com>
> mjwall@gmail.com> wrote:
>
> Andrew,
>
> The commons-vfs 2.1 jar broke the accumulo build in 1.6.6 using the hadoop
> 1 profile.  That profile is remove in 1.7+, so the commons-vfs update was
> left out of 1.6.6.  You should just replace the commons-vfs jar in your
> deployment.  See  <https://issues.apache.org/jira/browse/ACCUMULO-3470>
> https://issues.apache.org/jira/browse/ACCUMULO-3470
>
> Mike
>
> On Fri, Dec 2, 2016 at 10:27 AM, Andrew Hulbert <ahulbert@ccri.com> wrote:
>
> Hi all,
>
> It appears that the commons-vfs2 jar that ships with the 1.6.6 binary
> tar.gz is still version 2.0 according the the META-INF/MANIFEST.MF and
> other maven artifacts in the META-INF instead of 2.1 which is what I
> thought it should be according to the release notes.
>
> Wondering if this is something that can be fixed in the distro or would it
> require a new 1.6.7 release?
>
> Andrew
>
>
>
>
>

Mime
View raw message