Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1497925321.1242156525580.JavaMail.jira@brutus>
Date: Tue, 12 May 2009 12:28:45 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1403) Move transactional and indexer hbase
 out of core into contrib or out to their own project
In-Reply-To: <1128480939.1242059985614.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708579#action_12708579 ] 

stack commented on HBASE-1403:
------------------------------

Can we do these markings as Types in the new KeyValue?  Before serializing we could AND the key type with source.  How many bits do you need?  Clint, what about you doing your types in same way?  AND'ing or a new type.

If KeyValue.Type will do it, lets make the changes now before 0.20.0 release.

> Move transactional and indexer hbase out of core into contrib or out to their own project
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-1403
>                 URL: https://issues.apache.org/jira/browse/HBASE-1403
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: stack
>
> Its a bit of work bringing along these hbase subclasses as changes happen in core.  They are substantial enough contributions, they could be their own projects -- if there was the will to keep them up.  Otherwise, we could move them down into contrib. -- that'd better demark core and this hbase customizations.
> I wrote Clint asking what he thought.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.