You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/15 22:17:30 UTC

[jira] [Resolved] (HBASE-1788) [stargate] multipart binary encoding option

     [ https://issues.apache.org/jira/browse/HBASE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-1788.
-----------------------------------

    Resolution: Later
      Assignee:     (was: Andrew Purtell)

There doesn't seem to be any need for this, and nothing I require.
                
> [stargate] multipart binary encoding option
> -------------------------------------------
>
>                 Key: HBASE-1788
>                 URL: https://issues.apache.org/jira/browse/HBASE-1788
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Andrew Purtell
>            Priority: Trivial
>
> Add support for multipart/related encoded entity bodies.
> There is support already for binary encoding also but not multipart  -- operations with application/octet-stream encoding are limited to single KVs. 
> Multipart/related is not necessarily efficient. Timestamps and column names would be sent as X-headers mixed between the binary blobs, and the part headers and border adds more overhead. The only reason to support it is if someone cannot use protobufs as an alternative to XML.

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