[
https://issues.apache.org/jira/browse/HBASE-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180166#comment-13180166
]
Zhihong Yu commented on HBASE-5122:
-----------------------------------
Since ColumnInterpreters aren't limited to specific tables, approach from
HBASE-4554 cannot be used here.
I thought of adding load method in RegionCoprocessorHost for
ColumnInterpreters. But RegionCoprocessorHost only loads system and table
coprocessors in its ctor.
May need advice from coprocessor gurus about the proper solution.
> Provide flexible method for loading ColumnInterpreters
> ------------------------------------------------------
>
> Key: HBASE-5122
> URL: https://issues.apache.org/jira/browse/HBASE-5122
> Project: HBase
> Issue Type: Task
> Reporter: Zhihong Yu
>
> See the discussion on user list entitled 'AggregateProtocol Help'
> From Royston:
> {noformat}
> I re-created my HBase table to contain Bytes.toBytes(Long) values and that
> fixed it.
> {noformat}
> It was not the intention when AggregateProtocol was designed that users have
> to change their schema to match LongColumnInterpreter.
> This JIRA aims to provide a flexible way for users to load their custom
> ColumnInterpreters into region servers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
