[
https://issues.apache.org/jira/browse/HBASE-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093610#comment-14093610
]
Hudson commented on HBASE-11716:
--------------------------------
SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #418 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/418/])
HBASE-11716 LoadTestDataGeneratorWithVisibilityLabels should handle Delete
mutations (Anoop Sam John) (apurtell: rev
93390aca70a2780fd1a017a8db28ad9b01a808fc)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/LoadTestDataGeneratorWithVisibilityLabels.java
> LoadTestDataGeneratorWithVisibilityLabels should handle Delete mutations
> ------------------------------------------------------------------------
>
> Key: HBASE-11716
> URL: https://issues.apache.org/jira/browse/HBASE-11716
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.5
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Labels: IntegrationTest
> Fix For: 0.99.0, 2.0.0, 0.98.6
>
> Attachments: HBASE-11716.patch
>
>
> {code}
> public Mutation beforeMutate(long rowkeyBase, Mutation m) throws
> IOException {
> if (!(m instanceof Delete)) {
> m.setCellVisibility(new CellVisibility(this.visibilityExps[(int)
> rowkeyBase
> % this.visibilityExps.length]));
> }
> return m;
> }
> {code}
> Now we have delete CellVisibility matching and so we should add
> CellVisibility for Mutations also. Just removing the if check part will solve
> the issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
