[
https://issues.apache.org/jira/browse/HBASE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708553#action_12708553
]
stack commented on HBASE-1403:
------------------------------
Above seems reasonable to me -- especially the bit where its keeping us honest
regards API.
In truth, changing THBase and ITHBase is not that much work its just that I'm
afraid I'll break it or just not give it the attention it needs.
We might instead work on moving THBase and ITHBase pollution that is up in core
out and down into the THBase and ITHBase implementations. I'm thinking of the
HLog and HCD. HLog values are a HLogEdit which is now just the new KeyValue
class + a THBase flag. In interests of performance, I'd like to not have to
create a HLogEdit at all and just shove in the KeyValue. If THBase needs more
than that, lets make it so you can do it in subclass. Similarly for HCD.
Every toString includes the bit about indexes -- an ITHBase-ism.
Good stuff Clint.
> 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.
