hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9136) RPC side changes to have a different codec for server to client communication
Date Sat, 28 Sep 2013 05:11:03 GMT

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

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

Not sure whether we can always make the server not to return the tags back to the callee.
 Take the case of Export tool which will create an MR based scan. In this case the server
should return the tags also along with KV so that tags will also get exported. Basically the
client should be able to tell whether it needs the tags back or not.  Making it more generic
the client should be able to specify a Codec to be used(?) using the Encoder server will write
and client will use the corresponding Decoder in the Codec.
                
> 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
>
>         Attachments: HBASE-9136.patch
>
>
> 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