[
https://issues.apache.org/jira/browse/HBASE-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731047#comment-13731047
]
ramkrishna.s.vasudevan commented on HBASE-9136:
-----------------------------------------------
>>We shuttle the KVs across using a different API. Could Codec figure this out?
Yes. May be like how WAL does by passing the Compression to the codec and
checking it for null and calling different encoder and decoder?
This would mean that we would get different implementation for the same codec?
But in the RPC layer we would not be able to differentiate the options.
Let me think through on this more and comment here.
> 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
