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-18948) HBase tags are server side only.
Date Fri, 06 Oct 2017 06:31:00 GMT

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

Anoop Sam John commented on HBASE-18948:

bq.We allow clients to build raw cell serializations, potentially including tags, and submit
them. I can't say if they are stripped out or not.
It is stripped out now.  And ya while sending back read response also, at the RPC layer the
tags are getting stripped off ( by Codec)
And ya replication uses special Codec so as to pass Tags. And ReplicationEP will be getting
this used I believe.
And YES. When the read cells are passed through the CP hooks or a CP code is doing a read,
the Tags will be visible in the Cells.  Only at the RPC layer the stripping happens.
I agree that this is a temp solution for not exposing the security related tags to client.
But that is not full fledged.  Planned to do cleanup and completion of this for 2.0 but seems
wont happen as am in to some thing else now.

> HBase tags are server side only.
> --------------------------------
>                 Key: HBASE-18948
>                 URL: https://issues.apache.org/jira/browse/HBASE-18948
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Thiriguna Bharat Rao
>            Assignee: Thiriguna Bharat Rao
>            Priority: Minor
>             Fix For: 3.0.0
>         Attachments: HBASE-18948.patch
> HBase tags are server side only. In the Apache HBase documentation, in section 62.1.1
http://hbase.apache.org/book.html#_implementation_details , I am going to add a sentence to
state explicitly that "Tags are not available for get/set from client operations including

This message was sent by Atlassian JIRA

View raw message