Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 12109 invoked from network); 5 Feb 2010 02:20:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Feb 2010 02:20:27 -0000 Received: (qmail 98991 invoked by uid 500); 5 Feb 2010 02:20:26 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 98928 invoked by uid 500); 5 Feb 2010 02:20:26 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 98918 invoked by uid 99); 5 Feb 2010 02:20:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 02:20:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lars.francke@gmail.com designates 74.125.78.26 as permitted sender) Received: from [74.125.78.26] (HELO ey-out-2122.google.com) (74.125.78.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Feb 2010 02:20:18 +0000 Received: by ey-out-2122.google.com with SMTP id 22so406723eye.23 for ; Thu, 04 Feb 2010 18:19:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=Y3EJ1ZwPOXEWyGCiW++Q24QGt9vFOPlxeJuUXO6UxLc=; b=kXtXI+gq6jNr78Q38E9lOLL+/klcnYIvj0hgTLDg1EcMT7t6Ud5HeGwEIS+7Fx1h63 kf93qm93XRYoDndAPinRpHlzBNnQ89+22ULtrgiX4uPDOVlAswrE91vQbHM39ryvPGiG WgNe2uHdNMijBWk251XmAfabVNkMoJ7qBGKvw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Gp3jk6AtU/ZlYCOYH568RSIgbG+TJMlZ/KEwMGbV0Oumj0gxFgjI7jdFodHokVGlKc xb9fFZLtwbudRi2IcZVjj+Pa2zKwsxP7FGwiLYhN2m0+KbvSUgnSfcU9vlUTL6lY5eLo B2OumLP6SbyGyfzRejs4/FZLa45Nzpxg8EFk0= MIME-Version: 1.0 Received: by 10.216.85.213 with SMTP id u63mr1121972wee.15.1265336398128; Thu, 04 Feb 2010 18:19:58 -0800 (PST) In-Reply-To: <7c962aed1002041350ya29cb0as1f8495c51b71b6c2@mail.gmail.com> References: <7c962aed1001281238g2c49d660pf47d23fe90432886@mail.gmail.com> <7c962aed1002041350ya29cb0as1f8495c51b71b6c2@mail.gmail.com> From: Lars Francke Date: Fri, 5 Feb 2010 03:19:38 +0100 Message-ID: Subject: Re: Discussion: Move contribs out of hbase? To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org > + Move those contribs we consider core -- stargate for example -- up > into core and out of contrib (thrift is a little more involved; > depends on how Lars Francke wants to run it) I've kept quiet so far as I am neither a committer nor a big time contributor nor a long standing member of the HBase community. I also have no strong opinion about contrib vs. core in general and thrift contrib in particular. In which way is Thrift more involved than Stargate? The code itself is easily decoupled from the core as it uses only the public API via interfaces. The only slightly complex thing at the moment is that we'll keep the old API around for now so that we'll probably need a "thrift2" package or something like that. It was decided earlier (in one of the tickets) that the old API should stay in core for 0.21 anyway. Either way: If Stargate gets pulled in the core I think thrift should stay too but as I said before I'm fine either way. Cheers, Lars