[
https://issues.apache.org/jira/browse/HBASE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273945#comment-13273945
]
Hadoop QA commented on HBASE-5385:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12526622/HBASE-5385-v3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop23. The patch compiles against the hadoop 0.23.x profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 31 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.TestDrainingServer
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1860//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1860//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1860//console
This message is automatically generated.
> Delete table/column should delete stored permissions on -acl- table
> ---------------------------------------------------------------------
>
> Key: HBASE-5385
> URL: https://issues.apache.org/jira/browse/HBASE-5385
> Project: HBase
> Issue Type: Sub-task
> Components: security
> Affects Versions: 0.94.0
> Reporter: Enis Soztutar
> Assignee: Matteo Bertozzi
> Attachments: 5385-v3.patch, HBASE-5385-v0.patch, HBASE-5385-v1.patch,
> HBASE-5385-v2.patch, HBASE-5385-v3.patch
>
>
> Deleting the table or a column does not cascade to the stored permissions at
> the -acl- table. We should also remove those permissions, otherwise, it can
> be a security leak, where freshly created tables contain permissions from
> previous same-named tables. We might also want to ensure, upon table
> creation, that no entries are already stored at the -acl- table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
