You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (Updated) (JIRA)" <ji...@apache.org> on 2012/03/21 18:13:40 UTC
[jira] [Updated] (HBASE-5122) Provide flexible method for loading
ColumnInterpreters
[ https://issues.apache.org/jira/browse/HBASE-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-5122:
---------------------------------
Fix Version/s: (was: 0.94.0)
0.96.0
> 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
> Fix For: 0.96.0
>
>
> 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