Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 128AD10527 for ; Tue, 20 Aug 2013 22:25:53 +0000 (UTC) Received: (qmail 54797 invoked by uid 500); 20 Aug 2013 22:25:52 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 54764 invoked by uid 500); 20 Aug 2013 22:25:52 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 54755 invoked by uid 99); 20 Aug 2013 22:25:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 22:25:52 +0000 Date: Tue, 20 Aug 2013 22:25:52 +0000 (UTC) From: "James Taylor (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8693) DataType: provide extensible type API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745535#comment-13745535 ] James Taylor commented on HBASE-8693: ------------------------------------- Yes, Phoenix would plan to use the Struct and StructIterator. Rather than the client needing to modify the iteration code everywhere, it'd be good if the StructIterator handled this out-of-the-box. On the write side of things, it'd be good if the thing that writes a Struct striped off trailing nulls. You can only do this when writing the key is complete, because of course you might have nulls in the middle which is valid. I don't mean to push everything back to your framework, but the important thing is that the framework writes in the expected way already. If Phoenix has to specialize it, then we lose the interop piece which is what we're trying to get in the first place. > DataType: provide extensible type API > ------------------------------------- > > Key: HBASE-8693 > URL: https://issues.apache.org/jira/browse/HBASE-8693 > Project: HBase > Issue Type: Sub-task > Components: Client > Reporter: Nick Dimiduk > Assignee: Nick Dimiduk > Priority: Blocker > Fix For: 0.98.0, 0.95.2 > > Attachments: 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0001-HBASE-8693-Extensible-data-types-API.patch, 0002-HBASE-8693-example-Use-DataType-API-to-build-regionN.patch, KijiFormattedEntityId.java > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira