[
https://issues.apache.org/jira/browse/HBASE-16055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346053#comment-15346053
]
ramkrishna.s.vasudevan commented on HBASE-16055:
------------------------------------------------
bq.So here the user account, with which the Reducer gets run, should have
SYSTEM visibility label. We have to document that as well?
Yes. Infact interacting that User I wanted to raise the JIRA. Will raise one
and have some things to discuss with respect to it.
bq.Chances are less, still if the cell is already having some tags with it, we
should not be loosing them.
Here we will not be having any tags. Because these cells are from Puts.
currently we don't support Tags to be added with Puts. So should be fine I
think.
> PutSortReducer loses any Visibility/acl attribute set on the Puts
> ------------------------------------------------------------------
>
> Key: HBASE-16055
> URL: https://issues.apache.org/jira/browse/HBASE-16055
> Project: HBase
> Issue Type: Bug
> Components: security
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0, 1.0.4, 1.4.0, 0.98.21
>
> Attachments: HBASE-16055_1.patch
>
>
> Based on a user discussion, I think as the user pointed out rightly, when a
> PutSortReducer is used any visibility attribute or external attribute set on
> the Put will be lost as we create KVs out of the cells in the puts whereas
> the ACL and visibility are all set as Attributes.
> In TextSortReducer we tend to read the information we tend to read the
> information from the parsed line but here in PutSortReducer we don't do it. I
> think this problem should be in all the existing versions where we support
> Tags. Correct me if am wrong here.
> [~anoop.hbase], [[email protected]]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
