[
https://issues.apache.org/jira/browse/HBASE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733225#comment-13733225
]
ramkrishna.s.vasudevan commented on HBASE-9136:
-----------------------------------------------
One way to do this is while creating the RPCClient make it aware whether it is
on the client side or on the server side.
Use this information to initialize a different codec if that new codec is set
if not go with the default codec.
Another way could be, based on the RPCClient that is created(i.e whether it is
on client side or on the server side), set this information to the codec class.
So handle this flag inside the codec as what to do if the codec is set for a
server or for the client.
In case of replication, at least for the tag case the tag part should also be
written.
> 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
