hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9136) RPC side changes to have a different codec for server to client communication
Date Thu, 05 Sep 2013 15:47:53 GMT

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

ramkrishna.s.vasudevan commented on HBASE-9136:
-----------------------------------------------

Yes Stack.  We have a patch for this.
Exactly we have done what you have suggest.  So both client and server would instantiate two
codecs.  One that comes from the header and the other that comes from the configuration.
So local Context and remote Context both would be available.  
So its like a two way communication.  I can attach a patch for this.  
                
> RPC side changes to have a different codec for server to client communication
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-9136
>                 URL: https://issues.apache.org/jira/browse/HBASE-9136
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 0.98.0
>
>
> With reference to the mail sent in the dev list,
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.devel/38984
> We should have a provision such that the codec on the server side could be different
from the one on the client side.  This would help to remove the tags for security usecases.
 
> This JIRA is aimed to provide that capability in the codec itself.

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

Mime
View raw message