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

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

bq.Anoop fed me the above off line.  It just seems wrong that codec need know 
if 'server' or 'client'.  Why can't it be TagsCodec and StripTagsCodec and then 
at the various junctions (client sending, server receiving, WAL writing, etc.) 
they read configuration what Codec to use or what code to use Decoding a 
particular Encoder; e.g. on server, we'd write back to the client using 
NoTagsKVCodec.
True.. But this I think has to happen with codec negotiation.  Only then the 
server and the client will know about each other what the other is using.  
TagsCodec and StripTagsCodec has to be specified in a configuration (which I 
call it as a mapping - Anoop does not like that :)) and use that on either 
side. 
May be we can see how costly is stripping out the tags from every kv in the 
CPs.. we can benchmark it once?

> Strip tags from KV while sending back to client on reads
> --------------------------------------------------------
>
>                 Key: HBASE-10322
>                 URL: https://issues.apache.org/jira/browse/HBASE-10322
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>            Priority: Blocker
>             Fix For: 0.98.0, 0.99.0
>
>         Attachments: HBASE-10322.patch
>
>
> Right now we have some inconsistency wrt sending back tags on read. We do 
> this in scan when using Java client(Codec based cell block encoding). But 
> during a Get operation or when a pure PB based Scan comes we are not sending 
> back the tags.  So any of the below fix we have to do
> 1. Send back tags in missing cases also. But sending back visibility 
> expression/ cell ACL is not correct.
> 2. Don't send back tags in any case. This will a problem when a tool like 
> ExportTool use the scan to export the table data. We will miss exporting the 
> cell visibility/ACL.
> 3. Send back tags based on some condition. It has to be per scan basis. 
> Simplest way is pass some kind of attribute in Scan which says whether to 
> send back tags or not. But believing some thing what scan specifies might not 
> be correct IMO. Then comes the way of checking the user who is doing the 
> scan. When a HBase super user doing the scan then only send back tags. So 
> when a case comes like Export Tool's the execution should happen from a super 
> user.
> So IMO we should go with #3.
> Patch coming soon.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to