hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clint Morgan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1403) Move transactional and indexer hbase out of core into contrib or out to their own project
Date Tue, 12 May 2009 18:15:45 GMT

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

Clint Morgan commented on HBASE-1403:

Pasting in my response to stack:

I can understand the feeling from the core developers like they have to do extra work to keep
the sub-servers working. But is it really that cumbersome?

Everything else being equal, I'd prefer to keep the stuff inside hbase-core. One reason is
that it will help dissuade breaking changes to the relevant parts of the API. Another is increased
visibility to attract new users/developers.

I can pitch in to get the servers working again for 0.20 if need be.  It seemed straightforward
when I got them working in trunk a few weeks ago.

But ultimately its the core-dev's call as to what is best for the hbase community. If ya'll
feel that the servers are too much a burden, then I can live with it as an outside extension.

> 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.

View raw message