You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2013/08/06 09:26:49 UTC

[jira] [Commented] (HBASE-9136) RPC side changes to have a different codec for server to client communication

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

Anoop Sam John commented on HBASE-9136:
---------------------------------------

Ram

As Stack said in the dev mailing list  (Could the codec itself figure its context and act appropriately)  that would be better??  Is ur idea that Encoder in the codec at RS does not write tags?   Then Replication will be an issue. During Replication teh encoder should write the Tags to the peer cluster
                
> 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