[jira] [Commented] (SENTRY-583) Add boundary condition test coverage to HDFS synchronization test suite around max #of groups

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on SENTRY-583:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12697164/SENTRY-583-4.patch against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to build with patch (exit code 1)

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/836/console

This message is automatically generated.

> Add boundary condition test coverage to HDFS synchronization test suite around max #of groups
> ---------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-583
>                 URL: https://issues.apache.org/jira/browse/SENTRY-583
>             Project: Sentry
>          Issue Type: Test
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Lenni Kuff
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-583-0.patch, SENTRY-583-1.patch, SENTRY-583-2.patch, SENTRY-583-3.patch, SENTRY-583-4.patch
>
>
> Normally, HDFS ACLs has a limit of 32 entries per object (HDFS-5617), but this limit should not be enforced when using Sentry HDFS synchronization. I verified that this works, but we should add a test case to cover this scenario. Something like:
> # Grant to >32 unique groups to a table
> # Verify -getfacls returns all items
> It would also be interesting to see what happens when a new table is created when a database has been granted >32 groups. The new table's directory will inherit the permissions from the directory and I would assume that when the feature is disabled some of these will be missing. It would be good to verify that things don't blow up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)