Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3CE50200CD9 for ; Thu, 3 Aug 2017 19:17:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3B6A516C128; Thu, 3 Aug 2017 17:17:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8303016C125 for ; Thu, 3 Aug 2017 19:17:51 +0200 (CEST) Received: (qmail 70825 invoked by uid 500); 3 Aug 2017 17:17:50 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 70814 invoked by uid 99); 3 Aug 2017 17:17:50 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2017 17:17:50 +0000 Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 42E081A0129 for ; Thu, 3 Aug 2017 17:17:50 +0000 (UTC) Received: by mail-vk0-f47.google.com with SMTP id u133so7658538vke.3 for ; Thu, 03 Aug 2017 10:17:50 -0700 (PDT) X-Gm-Message-State: AIVw110JJZfohS5dliRNDTGY1DYCkeq+amjs6bn7nS1P8kpOtbeUk1T2 /pkl+Epht327zNmTP17s3cs5HY5Nfg== X-Received: by 10.31.78.65 with SMTP id c62mr1540459vkb.6.1501780669552; Thu, 03 Aug 2017 10:17:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Date: Thu, 03 Aug 2017 17:17:39 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Hadoop 3 and our dependencies generally To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary="001a114d9b8e56df780555dc8ff6" archived-at: Thu, 03 Aug 2017 17:17:52 -0000 --001a114d9b8e56df780555dc8ff6 Content-Type: text/plain; charset="UTF-8" +1 from me, too, but I'd like to review what actually changes in master for the migration to happen. I don't know much about Hadoop 3. I'm curious what the releases will look like (AFAIK, it's only snapshot builds right now; is that correct?), how our dependencies will change, and what API stability guarantees it offers. On Thu, Aug 3, 2017 at 12:59 PM Josh Elser wrote: > +1 sounds like a good idea to me. > > On 8/3/17 10:08 AM, Sean Busbey wrote: > > Hi Folks! > > > > I think we need to start being more formal in planning for Hadoop 3. > > They're up to 3.0.0-alpha4 and are pushing towards API-locking betas[1]. > > > > What do folks think about starting to push on an Accumulo 2.0 release > that > > only supports Hadoop 3? It would let us move faster, which we'll need to > do > > if we want to get any API changes in to the Hadoop 3 line. > > > > If we get started soon we can probably make it parity on beta/GA status > > with the Hadoop 3 line. That would give us a beta for Accumulo Summit and > > GA by end of the year. > > > > Going to just Hadoop 3+ would also be a sufficient dependency break that > we > > could do a pass updating any lagging dependencies to latest major > version. > > > > > > [1]: > https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.0.0+release > > > --001a114d9b8e56df780555dc8ff6--