Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 8 Sep 2015 17:05:46 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12537193.1325688926000.280792.1441731946095@Atlassian.JIRA>
In-Reply-To: <JIRA.12537193.1325688926000@Atlassian.JIRA>
References: <JIRA.12537193.1325688926000@Atlassian.JIRA>
 <JIRA.12537193.1325688926996@arcas>
Subject: [jira] [Resolved] (HBASE-5122) Provide flexible method for loading
 ColumnInterpreters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)