You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/08 19:05:46 UTC

[jira] [Resolved] (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 ]

stack resolved HBASE-5122.
--------------------------
    Resolution: Later

Resolving old issue with not progress as later. Reopen if I have it wrong.

> Provide flexible method for loading ColumnInterpreters
> ------------------------------------------------------
>
>                 Key: HBASE-5122
>                 URL: https://issues.apache.org/jira/browse/HBASE-5122
>             Project: HBase
>          Issue Type: Task
>            Reporter: Ted 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 was sent by Atlassian JIRA
(v6.3.4#6332)