Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 50E6C10910 for ; Thu, 24 Oct 2013 16:35:46 +0000 (UTC) Received: (qmail 80834 invoked by uid 500); 24 Oct 2013 16:35:44 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 80802 invoked by uid 500); 24 Oct 2013 16:35:39 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 80794 invoked by uid 99); 24 Oct 2013 16:35:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Oct 2013 16:35:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Oct 2013 16:35:30 +0000 Received: by mail-vb0-f47.google.com with SMTP id m10so1422631vbh.20 for ; Thu, 24 Oct 2013 09:35:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=CIsUqt+y+KHZGVKCxRFDVwHXNkmW20ToRkF3IjSDJ0o=; b=hI13HmkJzdVaxP5/TtCdxtFOnA8mSntjeozAfQMwRkOyZvgmy5etyp9uTMyb52rTLH xU1cdD96EZd1FIjiGuGNt4U7CkZI560Oti/DI1voBNj0D2orOV41lCjpZrMMJC4nHSzj o9JXgXOAbeTx3Z2WGDwrgSZGNOHvebGYImnNQM+5TyUx3ft0NYuZAd/QWsQDx2ztj1fx 0iUa0FVJvMXZ0393AWCoUe8U7bLz3UQ/CvJ0JHSegEJ+MsVGkPcTkJMmHj32pap2/IkB ZThfRcUam/Y3YTrYzbsH2wJwju54OA0wZFCzpIju+hBfYh22uesQkCZkiqepgN7SvfGQ QCJA== X-Gm-Message-State: ALoCoQm8vKm2G01kdRchFSMuxYINee/LzgvY1LvY4+kGyDyouzE7rwl1ke//5v30COxcqET23vFo MIME-Version: 1.0 X-Received: by 10.52.52.137 with SMTP id t9mr1574009vdo.22.1382632508875; Thu, 24 Oct 2013 09:35:08 -0700 (PDT) Received: by 10.220.171.135 with HTTP; Thu, 24 Oct 2013 09:35:08 -0700 (PDT) In-Reply-To: <52685624.5020609@gmail.com> References: <52685624.5020609@gmail.com> Date: Thu, 24 Oct 2013 12:35:08 -0400 Message-ID: Subject: Re: [DISCUSS] Hadoop 2 and Accumulo 1.6.0 From: Keith Turner To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=089e0122f65e8c2ee704e97f3762 X-Virus-Checked: Checked by ClamAV on apache.org --089e0122f65e8c2ee704e97f3762 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Oct 23, 2013 at 7:05 PM, Josh Elser wrote: > To ensure that we get broader community interaction than only on a Jira > issue [1], I want to get community feedback about the version of Hadoop > which the default, deployed Accumulo artifacts will be compiled against. > Does Accumulo compiled against Hadoop-1 run against Hadoop-2 w/o recompilation or visa versa? If this does not work, then I suppose the jars we put into central will not work for some users. > > Currently, Accumulo builds against a Hadoop-1 series release > (1.5.1-SNAPSHOT and 1.6.0-SNAPSHOT build against 1.2.1, and 1.5.0 builds > against 1.0.4). Last week, the Apache Hadoop community voted to release > 2.2.0 as GA (general availability) -- in other words, the Apache Hadoop > community is calling Hadoop-2.2.0 "stable". > > As has been discussed across various issues on Jira, this means a few > different things for Accumulo. Most importantly, this serves as a > recommendation by us that users should be trying to use Hadoop-2.2.0 with > Accumulo 1.6.0. This does *not* mean that we do not support Hadoop1 ([2] > 1.2.1 specifically). Hadoop-1 support would still be "guaranteed" by us for > 1.6.0. > > - Josh > > [1] https://issues.apache.org/**jira/browse/ACCUMULO-1419 > [2] https://issues.apache.org/**jira/browse/ACCUMULO-1643 > --089e0122f65e8c2ee704e97f3762 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Wed, Oct 23, 2013 at 7:05 PM, Josh Elser <<= a href=3D"mailto:josh.elser@gmail.com" target=3D"_blank">josh.elser@gmail.c= om> wrote:
To ensure that we get broader community inte= raction than only on a Jira issue [1], I want to get community feedback abo= ut the version of Hadoop which the default, deployed Accumulo artifacts wil= l be compiled against.

Does Accumulo compiled against Hadoo= p-1 run against Hadoop-2 w/o recompilation or visa versa? =A0If this does n= ot work, then I suppose the jars we put into central will not work for some= users.
=A0

Currently, Accumulo builds against a Hadoop-1 series release (1.5.1-SNAPSHO= T and 1.6.0-SNAPSHOT build against 1.2.1, and 1.5.0 builds against 1.0.4). = Last week, the Apache Hadoop community voted to release 2.2.0 as GA (genera= l availability) -- in other words, the Apache Hadoop community is calling H= adoop-2.2.0 "stable".

As has been discussed across various issues on Jira, this means a few diffe= rent things for Accumulo. Most importantly, this serves as a recommendation= by us that users should be trying to use Hadoop-2.2.0 with Accumulo 1.6.0.= This does *not* mean that we do not support Hadoop1 ([2] 1.2.1 specificall= y). Hadoop-1 support would still be "guaranteed" by us for 1.6.0.=

- Josh

[1] https://issues.apache.org/jira/browse/ACCUMULO-1419<= br> [2] https://issues.apache.org/jira/browse/ACCUMULO-1643<= br>

--089e0122f65e8c2ee704e97f3762--