You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars Francke (JIRA)" <ji...@apache.org> on 2009/12/03 01:57:20 UTC

[jira] Commented: (HBASE-1373) Update Thrift to use compact/framed protocol

    [ https://issues.apache.org/jira/browse/HBASE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785096#action_12785096 ] 

Lars Francke commented on HBASE-1373:
-------------------------------------

As far as I know this protocol is only implemented for C++, Ruby and Java so I wouldn't use it as a standard option (mostly because I need Python ;-) ) but as I am rewriting the Thrift interface anyway (HBASE-1744) I could add an option to choose between the current binary and the new compact protocol at startup. If needed two instances could be started on two different ports with different protocols. (Same goes for the FramedTransport which seems to be implemented for most languages)

Would that be okay?

> Update Thrift to use compact/framed protocol
> --------------------------------------------
>
>                 Key: HBASE-1373
>                 URL: https://issues.apache.org/jira/browse/HBASE-1373
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: thrift
>            Reporter: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.21.0
>
>
> TCompactProtocol/TFramedTransport and nonblocking server option promises better efficiency and performance improvements. Consider moving HBase Thrift bits to this when full platform support is ready for TCompactProtocol. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.