[jira] [Updated] (SENTRY-1514) Massive Solr Unit Test Failures found, disable them for now.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1514:

Fix Version/s: sentry-ha-redesign
   1.8.0

> Massive Solr Unit Test Failures found, disable them for now.
> 
>
> Key: SENTRY-1514
> URL: https://issues.apache.org/jira/browse/SENTRY-1514
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry, Solr Plugin, Test
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
>
> [Unit Test failure]fix 
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations
> {noformat}
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations  Time elapsed: 
> 6.254 sec  <<< ERROR!
> java.lang.IllegalStateException: No context information for thread: 
> Thread[id=1, name=main, state=RUNNABLE, group=main]. Is this thread running 
> under a class com.carrotsearch.randomizedtesting.RandomizedRunner runner 
> context? Add @RunWith(class 
> com.carrotsearch.randomizedtesting.RandomizedRunner.class) to your test 
> class. Make sure your code accesses random contexts within @BeforeClass and 
> @AfterClass boundary (for example, static test class initializers are not 
> permitted to access random contexts).
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.context(RandomizedContext.java:206)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.current(RandomizedContext.java:144)
>   at 
> org.apache.lucene.util.LuceneTestCase.getBaseTempDirForTestClass(LuceneTestCase.java:2525)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2569)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2557)
>   at 
> org.apache.solr.cloud.MiniSolrCloudCluster.(MiniSolrCloudCluster.java:104)
>   at 
> org.apache.sentry.tests.e2e.solr.AbstractSolrSentryTestBase.beforeTestSimpleSolrEndToEnd(AbstractSolrSentryTestBase.java:148)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



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

[jira] [Updated] (SENTRY-1514) Massive Solr Unit Test Failures found, disable them for now.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1514:

Component/s: Test
 Solr Plugin
 Sentry

> Massive Solr Unit Test Failures found, disable them for now.
> 
>
> Key: SENTRY-1514
> URL: https://issues.apache.org/jira/browse/SENTRY-1514
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry, Solr Plugin, Test
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
>
> [Unit Test failure]fix 
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations
> {noformat}
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations  Time elapsed: 
> 6.254 sec  <<< ERROR!
> java.lang.IllegalStateException: No context information for thread: 
> Thread[id=1, name=main, state=RUNNABLE, group=main]. Is this thread running 
> under a class com.carrotsearch.randomizedtesting.RandomizedRunner runner 
> context? Add @RunWith(class 
> com.carrotsearch.randomizedtesting.RandomizedRunner.class) to your test 
> class. Make sure your code accesses random contexts within @BeforeClass and 
> @AfterClass boundary (for example, static test class initializers are not 
> permitted to access random contexts).
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.context(RandomizedContext.java:206)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.current(RandomizedContext.java:144)
>   at 
> org.apache.lucene.util.LuceneTestCase.getBaseTempDirForTestClass(LuceneTestCase.java:2525)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2569)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2557)
>   at 
> org.apache.solr.cloud.MiniSolrCloudCluster.(MiniSolrCloudCluster.java:104)
>   at 
> org.apache.sentry.tests.e2e.solr.AbstractSolrSentryTestBase.beforeTestSimpleSolrEndToEnd(AbstractSolrSentryTestBase.java:148)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



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

[jira] [Created] (SENTRY-1514) Massive Solr Unit Test Failures found, disable them for now.

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1514:
---

 Summary: Massive Solr Unit Test Failures found, disable them for 
now.
 Key: SENTRY-1514
 URL: https://issues.apache.org/jira/browse/SENTRY-1514
 Project: Sentry
  Issue Type: Bug
Reporter: Anne Yu


[Unit Test failure]fix 
org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations

{noformat}
org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations  Time elapsed: 
6.254 sec  <<< ERROR!
java.lang.IllegalStateException: No context information for thread: 
Thread[id=1, name=main, state=RUNNABLE, group=main]. Is this thread running 
under a class com.carrotsearch.randomizedtesting.RandomizedRunner runner 
context? Add @RunWith(class 
com.carrotsearch.randomizedtesting.RandomizedRunner.class) to your test class. 
Make sure your code accesses random contexts within @BeforeClass and 
@AfterClass boundary (for example, static test class initializers are not 
permitted to access random contexts).
at 
com.carrotsearch.randomizedtesting.RandomizedContext.context(RandomizedContext.java:206)
at 
com.carrotsearch.randomizedtesting.RandomizedContext.current(RandomizedContext.java:144)
at 
org.apache.lucene.util.LuceneTestCase.getBaseTempDirForTestClass(LuceneTestCase.java:2525)
at 
org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2569)
at 
org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2557)
at 
org.apache.solr.cloud.MiniSolrCloudCluster.(MiniSolrCloudCluster.java:104)
at 
org.apache.sentry.tests.e2e.solr.AbstractSolrSentryTestBase.beforeTestSimpleSolrEndToEnd(AbstractSolrSentryTestBase.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
{noformat}



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

[jira] [Assigned] (SENTRY-1514) Massive Solr Unit Test Failures found, disable them for now.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu reassigned SENTRY-1514:
---

Assignee: Anne Yu

> Massive Solr Unit Test Failures found, disable them for now.
> 
>
> Key: SENTRY-1514
> URL: https://issues.apache.org/jira/browse/SENTRY-1514
> Project: Sentry
>  Issue Type: Bug
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> [Unit Test failure]fix 
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations
> {noformat}
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations  Time elapsed: 
> 6.254 sec  <<< ERROR!
> java.lang.IllegalStateException: No context information for thread: 
> Thread[id=1, name=main, state=RUNNABLE, group=main]. Is this thread running 
> under a class com.carrotsearch.randomizedtesting.RandomizedRunner runner 
> context? Add @RunWith(class 
> com.carrotsearch.randomizedtesting.RandomizedRunner.class) to your test 
> class. Make sure your code accesses random contexts within @BeforeClass and 
> @AfterClass boundary (for example, static test class initializers are not 
> permitted to access random contexts).
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.context(RandomizedContext.java:206)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.current(RandomizedContext.java:144)
>   at 
> org.apache.lucene.util.LuceneTestCase.getBaseTempDirForTestClass(LuceneTestCase.java:2525)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2569)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2557)
>   at 
> org.apache.solr.cloud.MiniSolrCloudCluster.(MiniSolrCloudCluster.java:104)
>   at 
> org.apache.sentry.tests.e2e.solr.AbstractSolrSentryTestBase.beforeTestSimpleSolrEndToEnd(AbstractSolrSentryTestBase.java:148)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



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

[jira] [Updated] (SENTRY-1514) Massive Solr Unit Test Failures found, disable them for now.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1514:

Affects Version/s: sentry-ha-redesign
   1.8.0

> Massive Solr Unit Test Failures found, disable them for now.
> 
>
> Key: SENTRY-1514
> URL: https://issues.apache.org/jira/browse/SENTRY-1514
> Project: Sentry
>  Issue Type: Bug
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> [Unit Test failure]fix 
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations
> {noformat}
> org.apache.sentry.tests.e2e.solr.TestCollAdminCoreOperations  Time elapsed: 
> 6.254 sec  <<< ERROR!
> java.lang.IllegalStateException: No context information for thread: 
> Thread[id=1, name=main, state=RUNNABLE, group=main]. Is this thread running 
> under a class com.carrotsearch.randomizedtesting.RandomizedRunner runner 
> context? Add @RunWith(class 
> com.carrotsearch.randomizedtesting.RandomizedRunner.class) to your test 
> class. Make sure your code accesses random contexts within @BeforeClass and 
> @AfterClass boundary (for example, static test class initializers are not 
> permitted to access random contexts).
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.context(RandomizedContext.java:206)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedContext.current(RandomizedContext.java:144)
>   at 
> org.apache.lucene.util.LuceneTestCase.getBaseTempDirForTestClass(LuceneTestCase.java:2525)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2569)
>   at 
> org.apache.lucene.util.LuceneTestCase.createTempDir(LuceneTestCase.java:2557)
>   at 
> org.apache.solr.cloud.MiniSolrCloudCluster.(MiniSolrCloudCluster.java:104)
>   at 
> org.apache.sentry.tests.e2e.solr.AbstractSolrSentryTestBase.beforeTestSimpleSolrEndToEnd(AbstractSolrSentryTestBase.java:148)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



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

[jira] [Updated] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1489:

   Resolution: Fixed
Fix Version/s: (was: sentry-ha-redesign)
   Status: Resolved  (was: Patch Available)

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1489.0.patch, SENTRY-1489.1.patch, 
> SENTRY-1489.2.patch
>
>




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

[jira] [Commented] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1489:
-

[~sravya], it takes a little time to sync, see here: 
https://github.com/apache/sentry/commit/b124675c0d571a4b85026d5390a7758092e04842

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1489.0.patch, SENTRY-1489.1.patch, 
> SENTRY-1489.2.patch
>
>




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

[jira] [Commented] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1489:
-

Thank you LiLi.

commit b124675c0d571a4b85026d5390a7758092e04842
Author: Anne Yu 
Date:   Fri Oct 28 13:44:06 2016 -0700

SENTRY-1489: Categorize e2e tests into slow and regular tests, so that can 
adapt the timeout and etc. (Anne Yu, reviewed by LiLi)

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1489.0.patch, SENTRY-1489.1.patch, 
> SENTRY-1489.2.patch
>
>




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

[jira] [Updated] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1489:

Attachment: SENTRY-1489.2.patch

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1489.0.patch, SENTRY-1489.1.patch, 
> SENTRY-1489.2.patch
>
>




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

[jira] [Commented] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1497:
-

Yes, I think so. I am doing more experiments using this tool now, will submit 
minor improvements later. Then cherry-pick to sentry-ha-redesign branch.

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch, SENTRY-1497.1.patch, 
> SENTRY-1497.2.patch, SENTRY-1497.3.patch, SENTRY-1497.4.patch
>
>




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

[jira] [Updated] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1489:

Attachment: SENTRY-1489.1.patch

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1489.0.patch, SENTRY-1489.1.patch
>
>




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

[jira] [Commented] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1497:
-

wiki: https://cwiki.apache.org/confluence/display/SENTRY/Test+Tools.

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch, SENTRY-1497.1.patch, 
> SENTRY-1497.2.patch, SENTRY-1497.3.patch, SENTRY-1497.4.patch
>
>




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

[jira] [Updated] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1497:

Attachment: SENTRY-1497.4.patch

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch, SENTRY-1497.1.patch, 
> SENTRY-1497.2.patch, SENTRY-1497.3.patch, SENTRY-1497.4.patch
>
>




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

[jira] [Updated] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1497:

Attachment: SENTRY-1497.2.patch

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch, SENTRY-1497.1.patch, 
> SENTRY-1497.2.patch
>
>




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

[jira] [Updated] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1497:

Attachment: SENTRY-1497.1.patch

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch, SENTRY-1497.1.patch
>
>




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

[jira] [Commented] (SENTRY-1498) Move SentryAdminServlet from sentry-service to sentry-provider

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1498:
-

Thanks, look good to me +1.

> Move SentryAdminServlet from sentry-service to sentry-provider
> --
>
> Key: SENTRY-1498
> URL: https://issues.apache.org/jira/browse/SENTRY-1498
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Li Li
>Assignee: Li Li
>Priority: Critical
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1498.001-sentry-ha-redesign.patch
>
>
> As sentry-ha-redesign branch does not have sentry-service dir which is 
> introduced in master branch, when merging SENTRY-1120 to sentry-ha-redesign 
> branch, SentryAdminServlet should be moved to 
> sentry-provider/sentry-provider-db. Now it breaks the mvn build and we should 
> fix it asap.



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

[jira] [Commented] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1497:
-

FYI, [~hsheinblatt].

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch
>
>




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

[jira] [Updated] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1497:

Status: Patch Available  (was: Open)

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch
>
>




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

[jira] [Updated] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1497:

Attachment: SENTRY-1497.0.patch

> create a sentry scale test tool to add various objects and privileges into 
> Sentry and HMS
> -
>
> Key: SENTRY-1497
> URL: https://issues.apache.org/jira/browse/SENTRY-1497
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1497.0.patch
>
>




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

[jira] [Created] (SENTRY-1497) create a sentry scale test tool to add various objects and privileges into Sentry and HMS

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1497:
---

 Summary: create a sentry scale test tool to add various objects 
and privileges into Sentry and HMS
 Key: SENTRY-1497
 URL: https://issues.apache.org/jira/browse/SENTRY-1497
 Project: Sentry
  Issue Type: Test
  Components: Sentry
Affects Versions: 1.8.0, sentry-ha-redesign
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: 1.8.0, sentry-ha-redesign






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

[jira] [Commented] (SENTRY-1490) Make tests more robust with respect to isolation

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1490:
-

[~lili] also suggested could add current time into the random string to make it 
unique.

> Make tests more robust with respect to isolation
> 
>
> Key: SENTRY-1490
> URL: https://issues.apache.org/jira/browse/SENTRY-1490
> Project: Sentry
>  Issue Type: Test
>Reporter: Sravya Tirukkovalur
>Assignee: Sravya Tirukkovalur
>Priority: Minor
>
> Traditionally in our e2e tests, each test class sets up the backend database. 
> And each test creates its own database and performs some operations and then 
> we clean up the databases created as part of the test either within the test 
> or in @After. 
> There are some problems with this approach: 
> - Not possible to run tests parallely, as more than one test can be using 
> same environment(db).
> - If tests do not clean up well, it leads to cascading test failures due to 
> incorrect assumptions.
> In the test TestDBNotificationListenerInBuiltDeserializer, I tried solving 
> this problem by creating a random name for db in each test case where dbname= 
> db+randomNumber. But the randomness does not seem to be sufficient as we are 
> not making sure the random numbers are non repeating. I am thinking of either 
> of the below solutions here:
> 1. Generate non repeating random names.
> 2. Use an atomic class integer rather than a random number.
> Can you think of any other simpler solutions?



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

[jira] [Commented] (SENTRY-1490) Make tests more robust with respect to isolation

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1490:
-

[~sravya] I created a random string including all ascii characters plus numbers 
as suffix. In that case if the length is n, theoretically we can have 1/256 ^ n 
probability to get duplicates. Hope this can help.

> Make tests more robust with respect to isolation
> 
>
> Key: SENTRY-1490
> URL: https://issues.apache.org/jira/browse/SENTRY-1490
> Project: Sentry
>  Issue Type: Test
>Reporter: Sravya Tirukkovalur
>Assignee: Sravya Tirukkovalur
>Priority: Minor
>
> Traditionally in our e2e tests, each test class sets up the backend database. 
> And each test creates its own database and performs some operations and then 
> we clean up the databases created as part of the test either within the test 
> or in @After. 
> There are some problems with this approach: 
> - Not possible to run tests parallely, as more than one test can be using 
> same environment(db).
> - If tests do not clean up well, it leads to cascading test failures due to 
> incorrect assumptions.
> In the test TestDBNotificationListenerInBuiltDeserializer, I tried solving 
> this problem by creating a random name for db in each test case where dbname= 
> db+randomNumber. But the randomness does not seem to be sufficient as we are 
> not making sure the random numbers are non repeating. I am thinking of either 
> of the below solutions here:
> 1. Generate non repeating random names.
> 2. Use an atomic class integer rather than a random number.
> Can you think of any other simpler solutions?



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

[jira] [Updated] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1489:

Status: Patch Available  (was: Open)

> Categorize e2e tests into slow and regular tests, so that can adapt the 
> timeout and etc.
> 
>
> Key: SENTRY-1489
> URL: https://issues.apache.org/jira/browse/SENTRY-1489
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1489.0.patch
>
>




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

[jira] [Created] (SENTRY-1489) Categorize e2e tests into slow and regular tests, so that can adapt the timeout and etc.

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1489:
---

 Summary: Categorize e2e tests into slow and regular tests, so that 
can adapt the timeout and etc.
 Key: SENTRY-1489
 URL: https://issues.apache.org/jira/browse/SENTRY-1489
 Project: Sentry
  Issue Type: Test
  Components: Sentry
Affects Versions: 1.8.0, sentry-ha-redesign
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: 1.8.0, sentry-ha-redesign






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

[jira] [Updated] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1488:

Attachment: SENTRY-1488.0.patch

> Create scripts that DBA can use to collect scale and usage stats
> 
>
> Key: SENTRY-1488
> URL: https://issues.apache.org/jira/browse/SENTRY-1488
> Project: Sentry
>  Issue Type: New Feature
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1488.0.patch, stats-1.png, stats-2.png
>
>
> We could create a script/tool subfolder so that can add side tools into it. 
> For example, we could simply create a script that gives us a row count of 
> every table in the Sentry database, plus the same thing for every table in 
> the Hive Metastore database. That will give us info like: total number of 
> tables, total number of roles, total permissions, etc.
> To start with:
> {code}
> #Roles
> #Permissions
> #Groups
> #Permissions per Role: avg, medium and max
> #Roles per Permission: avg, medium and max
> #Groups per role: avg, medium and max
> #Roles per group: avg, medium and max
> #Databases
> #Tables
> #Views
> #Partitions
> #Tables per Database: avg, medium and max
> #Views per Database: avg, medium and max
> #Partitions per Table: avg, medium and max
> {code}



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

[jira] [Updated] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1488:

Assignee: Anne Yu
  Status: Patch Available  (was: Open)

> Create scripts that DBA can use to collect scale and usage stats
> 
>
> Key: SENTRY-1488
> URL: https://issues.apache.org/jira/browse/SENTRY-1488
> Project: Sentry
>  Issue Type: New Feature
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1488.0.patch, stats-1.png, stats-2.png
>
>
> We could create a script/tool subfolder so that can add side tools into it. 
> For example, we could simply create a script that gives us a row count of 
> every table in the Sentry database, plus the same thing for every table in 
> the Hive Metastore database. That will give us info like: total number of 
> tables, total number of roles, total permissions, etc.
> To start with:
> {code}
> #Roles
> #Permissions
> #Groups
> #Permissions per Role: avg, medium and max
> #Roles per Permission: avg, medium and max
> #Groups per role: avg, medium and max
> #Roles per group: avg, medium and max
> #Databases
> #Tables
> #Views
> #Partitions
> #Tables per Database: avg, medium and max
> #Views per Database: avg, medium and max
> #Partitions per Table: avg, medium and max
> {code}



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

[jira] [Updated] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1488:

Attachment: stats-1.png
stats-2.png

> Create scripts that DBA can use to collect scale and usage stats
> 
>
> Key: SENTRY-1488
> URL: https://issues.apache.org/jira/browse/SENTRY-1488
> Project: Sentry
>  Issue Type: New Feature
>  Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Anne Yu
> Attachments: stats-1.png, stats-2.png
>
>
> We could create a script/tool subfolder so that can add side tools into it. 
> For example, we could simply create a script that gives us a row count of 
> every table in the Sentry database, plus the same thing for every table in 
> the Hive Metastore database. That will give us info like: total number of 
> tables, total number of roles, total permissions, etc.
> To start with:
> {code}
> #Roles
> #Permissions
> #Groups
> #Permissions per Role: avg, medium and max
> #Roles per Permission: avg, medium and max
> #Groups per role: avg, medium and max
> #Roles per group: avg, medium and max
> #Databases
> #Tables
> #Views
> #Partitions
> #Tables per Database: avg, medium and max
> #Views per Database: avg, medium and max
> #Partitions per Table: avg, medium and max
> {code}



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

[jira] [Created] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1488:
---

 Summary: Create scripts that DBA can use to collect scale and 
usage stats
 Key: SENTRY-1488
 URL: https://issues.apache.org/jira/browse/SENTRY-1488
 Project: Sentry
  Issue Type: New Feature
  Components: Sentry
Affects Versions: 1.8.0, sentry-ha-redesign
Reporter: Anne Yu


We could create a script/tool subfolder so that can add side tools into it. For 
example, we could simply create a script that gives us a row count of every 
table in the Sentry database, plus the same thing for every table in the Hive 
Metastore database. That will give us info like: total number of tables, total 
number of roles, total permissions, etc.

To start with:
{code}
#Roles
#Permissions
#Groups
#Permissions per Role: avg, medium and max
#Roles per Permission: avg, medium and max
#Groups per role: avg, medium and max
#Roles per group: avg, medium and max

#Databases
#Tables
#Views
#Partitions
#Tables per Database: avg, medium and max
#Views per Database: avg, medium and max
#Partitions per Table: avg, medium and max
{code}



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

[jira] [Resolved] (SENTRY-1431) Sentry HA test HMSFollower during failover

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu resolved SENTRY-1431.
-
   Resolution: Not A Problem
Fix Version/s: 1.8.0

The most recent  Sentry-872_design_v2_1.pdf changes this behavior. Not 
applicable anymore.

> Sentry HA test HMSFollower during failover
> --
>
> Key: SENTRY-1431
> URL: https://issues.apache.org/jira/browse/SENTRY-1431
> Project: Sentry
>  Issue Type: Task
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
>
> During Sentry service failover time period HMS follower should catch the 
> DDLs, DMLs related permissions in Sentry.



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

[jira] [Updated] (SENTRY-1424) Sentry HA client tests: master jira for all client related tests (retry, concurrency, correct exceptions etc.)

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1424:

Description: 
1. client can connect to active;
2. client can retry;
3. multiple clients can concurrent connect;
4. client can retry until find one active server;
5. client throws correct exceptions;
6. test pool client, not sure about the old client apis ?


  was:
1. client can connect to active;
2. client can't connect to passive;
3. multiple clients can connect to active;

Summary: Sentry HA client tests: master jira for all client related 
tests (retry, concurrency, correct exceptions etc.)  (was: Sentry HA client 
tests: ensure connect to active and block from passive)

> Sentry HA client tests: master jira for all client related tests (retry, 
> concurrency, correct exceptions etc.)
> --
>
> Key: SENTRY-1424
> URL: https://issues.apache.org/jira/browse/SENTRY-1424
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> 1. client can connect to active;
> 2. client can retry;
> 3. multiple clients can concurrent connect;
> 4. client can retry until find one active server;
> 5. client throws correct exceptions;
> 6. test pool client, not sure about the old client apis ?



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

[jira] [Comment Edited] (SENTRY-951) move hive warehouse dir to /hive, the dir doesn't have hive:hive as owner.

[Anne Yu (JIRA)]

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

Anne Yu edited comment on SENTRY-951 at 9/16/16 8:37 PM:
-

[~sravya], I just confirmed what you've described here on a real cluster 
installed with cdh5.7.0.


was (Author: anneyu):
[~sravya], I just confirmed what you've described here on a real cluster. 

> move hive warehouse dir to /hive, the dir doesn't have hive:hive as owner.
> --
>
> Key: SENTRY-951
> URL: https://issues.apache.org/jira/browse/SENTRY-951
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-951.0.test.patch
>
>
> {noformat}
> sudo -u hdfs hdfs dfs -mkdir -p /another
> sudo -u hdfs hdfs dfs -getfacl /another
> hfds:supergroup
> {noformat}
> put /another into hive.metastore.warehouse.dir;
> add /another into hdfs sentry syncup prefix;
> restart hive, sentry, hdfs
> {code}
> [root@anneyu-538-1 ~]# sudo -u hdfs hdfs dfs -getfacl /another
> # file: /another
> # owner: hdfs
> # group: supergroup
> user::rwx
> group::r-x
> other::r-x
> {code}
> If create table will get the below errors:
> {code}
> 0: jdbc:hive2://anneyu-538-4.vpc.cloudera.com> create table test7(s string);
> Error: Error while processing statement: FAILED: Execution Error, return code 
> 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got 
> exception: org.apache.hadoop.security.AccessControlException Permission 
> denied: user=hive, access=WRITE, inode="/another":hdfs:supergroup:drwxr-xr-x
> {code}



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

[jira] [Commented] (SENTRY-951) move hive warehouse dir to /hive, the dir doesn't have hive:hive as owner.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-951:


[~sravya], I just confirmed what you've described here on a real cluster. 

> move hive warehouse dir to /hive, the dir doesn't have hive:hive as owner.
> --
>
> Key: SENTRY-951
> URL: https://issues.apache.org/jira/browse/SENTRY-951
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-951.0.test.patch
>
>
> {noformat}
> sudo -u hdfs hdfs dfs -mkdir -p /another
> sudo -u hdfs hdfs dfs -getfacl /another
> hfds:supergroup
> {noformat}
> put /another into hive.metastore.warehouse.dir;
> add /another into hdfs sentry syncup prefix;
> restart hive, sentry, hdfs
> {code}
> [root@anneyu-538-1 ~]# sudo -u hdfs hdfs dfs -getfacl /another
> # file: /another
> # owner: hdfs
> # group: supergroup
> user::rwx
> group::r-x
> other::r-x
> {code}
> If create table will get the below errors:
> {code}
> 0: jdbc:hive2://anneyu-538-4.vpc.cloudera.com> create table test7(s string);
> Error: Error while processing statement: FAILED: Execution Error, return code 
> 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got 
> exception: org.apache.hadoop.security.AccessControlException Permission 
> denied: user=hive, access=WRITE, inode="/another":hdfs:supergroup:drwxr-xr-x
> {code}



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

[jira] [Updated] (SENTRY-1473) [test]: add more tests to test sentry supports only absolute path for now: s3://bucketname/ is correct; while s3://bucket is not

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1473:

Issue Type: Test  (was: Bug)

> [test]: add more tests to test sentry supports only absolute path for now: 
> s3://bucketname/ is correct; while s3://bucket is not
> 
>
> Key: SENTRY-1473
> URL: https://issues.apache.org/jira/browse/SENTRY-1473
> Project: Sentry
>  Issue Type: Test
>  Components: Sentry, Test
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
>




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

[jira] [Updated] (SENTRY-1473) [test]: add more tests to test sentry supports only absolute path for now: s3://bucketname/ is correct; while s3://bucket is not

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1473:

Summary: [test]: add more tests to test sentry supports only absolute path 
for now: s3://bucketname/ is correct; while s3://bucket is not  (was: sentry 
supports absolute path for now: s3://bucketname/ is correct; while s3://bucket 
is not)

> [test]: add more tests to test sentry supports only absolute path for now: 
> s3://bucketname/ is correct; while s3://bucket is not
> 
>
> Key: SENTRY-1473
> URL: https://issues.apache.org/jira/browse/SENTRY-1473
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry, Test
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>




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

[jira] [Updated] (SENTRY-1473) [test]: add more tests to test sentry supports only absolute path for now: s3://bucketname/ is correct; while s3://bucket is not

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1473:

 Assignee: Anne Yu
Affects Version/s: 1.8.0
  Component/s: Test
   Sentry

> [test]: add more tests to test sentry supports only absolute path for now: 
> s3://bucketname/ is correct; while s3://bucket is not
> 
>
> Key: SENTRY-1473
> URL: https://issues.apache.org/jira/browse/SENTRY-1473
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry, Test
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
>




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

[jira] [Created] (SENTRY-1473) sentry supports absolute path for now: s3://bucketname/ is correct; while s3://bucket is not

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1473:
---

 Summary: sentry supports absolute path for now: s3://bucketname/ 
is correct; while s3://bucket is not
 Key: SENTRY-1473
 URL: https://issues.apache.org/jira/browse/SENTRY-1473
 Project: Sentry
  Issue Type: Bug
Reporter: Anne Yu






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

[jira] [Commented] (SENTRY-1471) TestHDFSIntegrationBase.java implements HDFS ACL checking and query verification incorrectly

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1471:
-

[~vspec...@gmail.com], thanks for pointing out this issue. Since you've spent 
quite some time investigating the issue, do you have idea of after fix 
SENTRY-1471, why TestHDFSIntegrationAdvanced starts to fail? I guess this jira 
is meant to fix catch logic in verifyOnAllSubDirsHelper and verifyQuery APIs, 
but without fixing the test failures, this patch won't pass upstream-qa. Or do 
you have a jira filed already for real TestHDFSIntegrationAdvanced test 
failures? In that case, I can wait for it to be fixed.

> TestHDFSIntegrationBase.java implements HDFS ACL checking and query 
> verification incorrectly
> 
>
> Key: SENTRY-1471
> URL: https://issues.apache.org/jira/browse/SENTRY-1471
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Reporter: Vadim Spector
>Assignee: Anne Yu
>
> verifyOnAllSubDirsHelper() in TestHDFSIntegrationBase.java has a bug. When 
> the number of failed retries exceeds max value (the "else" portion of "if 
> (retry > 0)" statement, it erroneously assigns hasSucceeded = true. It means 
> that verifyOnAllSubDirsHelper() never returns false.
> Once the problem was fixed in a local development branch, several tests in 
> TestHDFSIntegrationAdvanced.java started failing. TestHDFSIntegrationEnd2End 
> tests are still ok.
> Also, it is unfortunate that TestHDFSIntegrationBase() returns boolean 
> instead of throwing the original AssertionError which contains information 
> about expected vs. found ACL permissions - this information is invaluable for 
> debugging. The fix is easy - the to-be-fixed "else" portion is inside the 
> "catch (Throwable th)" clause, so it should just re-throw caught exception. 
> This makes "hasSucceeded" variable unnecessary - verifyOnAllSubDirsHelper() 
> should have "void" return type.
> The same problem exists in verifyQuery(), also  in 
> TestHDFSIntegrationBase.java. The "else" clause of "if (retry > 0)" also 
> assigns "isSucceeded = true;" leading to the same problem - it never fails. 
> Suggested solution would be the same - just re-throw the exception. It will 
> not only fix the problem, but also make debugging easier. Current code 
> "Assert.assertTrue(isSucceeded);" throws away valuable information about the 
> expected vs detected number of database rows.
> Note: the above problems were introduced by SENTRY-1454. Suggested fixes 
> match the original code prior to SENTRY-1454.



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

[jira] [Comment Edited] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

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

Anne Yu edited comment on SENTRY-1454 at 9/12/16 10:06 PM:
---

commit 5cfd82d96e9baef51f7291d48e717c922baf2224
Author: Anne Yu 
Date:   Fri Aug 26 17:04:19 2016 -0700

SENTRY-1429, SENTRY-1454: fix flaky TestHDFSIntegration, refactor this huge 
test class, improve its cleanUp and setUp for temp HDFS dirs; divide test class 
into smoke test class and p2 test class; in post commit run, we will only run 
smoke tests.


was (Author: anneyu):
commit 5cfd82d96e9baef51f7291d48e717c922baf2224
Author: Anne Yu 
Date:   Fri Aug 26 17:04:19 2016 -0700

SENTRY-1429, SENTRY-1455: fix flaky TestHDFSIntegration, refactor this huge 
test class, improve its cleanUp and setUp for temp HDFS dirs; divide test class 
into smoke test class and p2 test class; in post commit run, we will only run 
smoke tests.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch, SENTRY-1429.4.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1464) Sentry e2e test failure in org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1464:

   Resolution: Fixed
Fix Version/s: 1.8.0
   Status: Resolved  (was: Patch Available)

Thank you [~hahao]:

commit a5ed6d912d1cac5f2239a629a34ce063ac97e6a4
Author: Anne Yu 
Date:   Thu Sep 8 14:44:25 2016 -0700

SENTRY-1464: fix Sentry e2e test failure in 
org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges;
 and print out key queries for triaging test failures on jenkins job's outputs. 
(Anne Yu, reviewed by Hao Hao).

> Sentry e2e test failure in 
> org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges
> ---
>
> Key: SENTRY-1464
> URL: https://issues.apache.org/jira/browse/SENTRY-1464
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1464.0.patch, SENTRY-1464.1.patch, 
> SENTRY-1464.2.patch
>
>
> {code}
> rror Message
> Error while compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
> Stacktrace
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException java.lang.IllegalArgumentException: 
> java.net.UnknownHostException: s3a
>   at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:241)
>   at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:227)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:244)
>   at 
> org.apache.sentry.tests.e2e.hive.TestUriPermissions.testAlterPartitionLocationPrivileges(TestUriPermissions.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: org.apache.hive.service.cli.HiveSQLException: Error while 
> compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:388)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:145)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:215)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:326)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:425)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:402)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:258)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:500)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1313)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1298)
>   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
>   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:746)
>   at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: 

[jira] [Updated] (SENTRY-1455) Fix TestConcurrentClients client initialization issue in test.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1455:

Attachment: (was: SENTRY-1464.2.patch)

> Fix TestConcurrentClients client initialization issue in test.
> --
>
> Key: SENTRY-1455
> URL: https://issues.apache.org/jira/browse/SENTRY-1455
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>
> {code}
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.grantPermissions(AbstractTestWithStaticConfiguration.java:398)]
>  Granting role to group: GRANT ROLE admin_role TO GROUP hive
> 2016-08-25 13:22:03,933 (Thread-10) [DEBUG - 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:148)]
>  Using server kerberos principal: sentry/localh...@vpc.cloudera.com
> 2016-08-25 13:22:03,946 (Thread-10) [ERROR - 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:315)] 
> SASL negotiation failure
> javax.security.sasl.SaslException: GSS initiate failed [Caused by 
> GSSException: No valid credentials provided (Mechanism level: Server not 
> found in Kerberos database (7) - UNKNOWN_SERVER)]
>   at 
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94)
>   at 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.baseOpen(SentryPolicyServiceClientDefaultImpl.java:126)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.open(SentryPolicyServiceClientDefaultImpl.java:104)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:162)
>   at 
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:48)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:567)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:564)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.getSentryClient(AbstractTestWithStaticConfiguration.java:563)
>   at 
> org.apache.sentry.tests.e2e.dbprovider.TestConcurrentClients.testConcurrentSentryClient(TestConcurrentClients.java:313)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: GSSException: No valid credentials provided (Mechanism level: 
> Server not found in Kerberos database (7) - UNKNOWN_SERVER)
> {code}



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

[jira] [Updated] (SENTRY-1455) Fix TestConcurrentClients client initialization issue in test.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1455:

Attachment: (was: SENTRY-1464.2.patch)

> Fix TestConcurrentClients client initialization issue in test.
> --
>
> Key: SENTRY-1455
> URL: https://issues.apache.org/jira/browse/SENTRY-1455
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
> Attachments: SENTRY-1464.2.patch
>
>
> {code}
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.grantPermissions(AbstractTestWithStaticConfiguration.java:398)]
>  Granting role to group: GRANT ROLE admin_role TO GROUP hive
> 2016-08-25 13:22:03,933 (Thread-10) [DEBUG - 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:148)]
>  Using server kerberos principal: sentry/localh...@vpc.cloudera.com
> 2016-08-25 13:22:03,946 (Thread-10) [ERROR - 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:315)] 
> SASL negotiation failure
> javax.security.sasl.SaslException: GSS initiate failed [Caused by 
> GSSException: No valid credentials provided (Mechanism level: Server not 
> found in Kerberos database (7) - UNKNOWN_SERVER)]
>   at 
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94)
>   at 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.baseOpen(SentryPolicyServiceClientDefaultImpl.java:126)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.open(SentryPolicyServiceClientDefaultImpl.java:104)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:162)
>   at 
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:48)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:567)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:564)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.getSentryClient(AbstractTestWithStaticConfiguration.java:563)
>   at 
> org.apache.sentry.tests.e2e.dbprovider.TestConcurrentClients.testConcurrentSentryClient(TestConcurrentClients.java:313)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: GSSException: No valid credentials provided (Mechanism level: 
> Server not found in Kerberos database (7) - UNKNOWN_SERVER)
> {code}



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

[jira] [Updated] (SENTRY-1455) Fix TestConcurrentClients client initialization issue in test.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1455:

Attachment: SENTRY-1464.2.patch

> Fix TestConcurrentClients client initialization issue in test.
> --
>
> Key: SENTRY-1455
> URL: https://issues.apache.org/jira/browse/SENTRY-1455
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>
> {code}
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.grantPermissions(AbstractTestWithStaticConfiguration.java:398)]
>  Granting role to group: GRANT ROLE admin_role TO GROUP hive
> 2016-08-25 13:22:03,933 (Thread-10) [DEBUG - 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:148)]
>  Using server kerberos principal: sentry/localh...@vpc.cloudera.com
> 2016-08-25 13:22:03,946 (Thread-10) [ERROR - 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:315)] 
> SASL negotiation failure
> javax.security.sasl.SaslException: GSS initiate failed [Caused by 
> GSSException: No valid credentials provided (Mechanism level: Server not 
> found in Kerberos database (7) - UNKNOWN_SERVER)]
>   at 
> com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.handleSaslStartMessage(TSaslClientTransport.java:94)
>   at 
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271)
>   at 
> org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.baseOpen(SentryPolicyServiceClientDefaultImpl.java:126)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl$UgiSaslClientTransport.open(SentryPolicyServiceClientDefaultImpl.java:104)
>   at 
> org.apache.sentry.provider.db.service.thrift.SentryPolicyServiceClientDefaultImpl.(SentryPolicyServiceClientDefaultImpl.java:162)
>   at 
> org.apache.sentry.service.thrift.SentryServiceClientFactory.create(SentryServiceClientFactory.java:48)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:567)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$3.run(AbstractTestWithStaticConfiguration.java:564)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:415)
>   at 
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.getSentryClient(AbstractTestWithStaticConfiguration.java:563)
>   at 
> org.apache.sentry.tests.e2e.dbprovider.TestConcurrentClients.testConcurrentSentryClient(TestConcurrentClients.java:313)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: GSSException: No valid credentials provided (Mechanism level: 
> Server not found in Kerberos database (7) - UNKNOWN_SERVER)
> {code}



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

[jira] [Commented] (SENTRY-1464) Sentry e2e test failure in org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1464:
-

Also added bullet proof in evaluating error message to remove exception from 
org.apache.sentry.tests.e2e.dbprovider.TestDbCrossOperations.org.apache.sentry.tests.e2e.dbprovider.TestDbCrossOperations.

org.apache.sentry.tests.e2e.dbprovider.TestDbCrossOperations.org.apache.sentry.tests.e2e.dbprovider.TestDbCrossOperations

Failing for the past 1 build (Since Unstable#5444 )
Took 3 min 56 sec.
add description
Stacktrace

java.lang.NullPointerException: null
at 
org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration$1.failed(AbstractTestWithStaticConfiguration.java:103)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:52)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:275)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:183)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

> Sentry e2e test failure in 
> org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges
> ---
>
> Key: SENTRY-1464
> URL: https://issues.apache.org/jira/browse/SENTRY-1464
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1464.0.patch
>
>
> {code}
> rror Message
> Error while compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
> Stacktrace
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException java.lang.IllegalArgumentException: 
> java.net.UnknownHostException: s3a
>   at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:241)
>   at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:227)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:244)
>   at 
> org.apache.sentry.tests.e2e.hive.TestUriPermissions.testAlterPartitionLocationPrivileges(TestUriPermissions.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: org.apache.hive.service.cli.HiveSQLException: Error while 
> compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:388)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:145)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:215)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:326)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:425)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:402)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:258)
>   at 
> 

[jira] [Updated] (SENTRY-1464) Sentry e2e test failure in org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1464:

Attachment: SENTRY-1464.0.patch

> Sentry e2e test failure in 
> org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges
> ---
>
> Key: SENTRY-1464
> URL: https://issues.apache.org/jira/browse/SENTRY-1464
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1464.0.patch
>
>
> {code}
> rror Message
> Error while compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
> Stacktrace
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException java.lang.IllegalArgumentException: 
> java.net.UnknownHostException: s3a
>   at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:241)
>   at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:227)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:244)
>   at 
> org.apache.sentry.tests.e2e.hive.TestUriPermissions.testAlterPartitionLocationPrivileges(TestUriPermissions.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: org.apache.hive.service.cli.HiveSQLException: Error while 
> compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:388)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:145)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:215)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:326)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:425)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:402)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:258)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:500)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1313)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1298)
>   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
>   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:746)
>   at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.hadoop.hive.ql.parse.SemanticException: 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.toReadEntity(BaseSemanticAnalyzer.java:1286)
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.toReadEntity(BaseSemanticAnalyzer.java:1278)
>   at 
> org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableAddParts(DDLSemanticAnalyzer.java:2774)
>   at 
> 

[jira] [Updated] (SENTRY-1464) Sentry e2e test failure in org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1464:

Status: Patch Available  (was: Open)

> Sentry e2e test failure in 
> org.apache.sentry.tests.e2e.dbprovider.TestDbUriPermissions.testAlterPartitionLocationPrivileges
> ---
>
> Key: SENTRY-1464
> URL: https://issues.apache.org/jira/browse/SENTRY-1464
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> {code}
> rror Message
> Error while compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
> Stacktrace
> org.apache.hive.service.cli.HiveSQLException: Error while compiling 
> statement: FAILED: SemanticException java.lang.IllegalArgumentException: 
> java.net.UnknownHostException: s3a
>   at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:241)
>   at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:227)
>   at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:244)
>   at 
> org.apache.sentry.tests.e2e.hive.TestUriPermissions.testAlterPartitionLocationPrivileges(TestUriPermissions.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>   at 
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> Caused by: org.apache.hive.service.cli.HiveSQLException: Error while 
> compiling statement: FAILED: SemanticException 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:388)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:145)
>   at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:215)
>   at 
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:326)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:425)
>   at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementAsync(HiveSessionImpl.java:402)
>   at 
> org.apache.hive.service.cli.CLIService.executeStatementAsync(CLIService.java:258)
>   at 
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:500)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1313)
>   at 
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1298)
>   at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
>   at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
>   at 
> org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:746)
>   at 
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.hadoop.hive.ql.parse.SemanticException: 
> java.lang.IllegalArgumentException: java.net.UnknownHostException: s3a
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.toReadEntity(BaseSemanticAnalyzer.java:1286)
>   at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.toReadEntity(BaseSemanticAnalyzer.java:1278)
>   at 
> org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableAddParts(DDLSemanticAnalyzer.java:2774)
>   at 
> org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:263)
>   at 
> 

[jira] [Comment Edited] (SENTRY-1457) DB, Table permission when connected with S3 storage on aws

[Anne Yu (JIRA)]

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

Anne Yu edited comment on SENTRY-1457 at 9/3/16 1:53 AM:
-

Seems Amazon S3 starts to support ACLs, similar to HDFS Acls: 
http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html. It will be 
helpful to support it as for Sentry + HDFS Synced Extended ACLs.


was (Author: anneyu):
Seems Amazon S3 starts to support ACLs, similar to HDFS Acls: 
http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html. It will be 
helpful to have it for Sentry + HDFS Synced Extended ACLs.

> DB, Table permission when connected with S3 storage on aws
> --
>
> Key: SENTRY-1457
> URL: https://issues.apache.org/jira/browse/SENTRY-1457
> Project: Sentry
>  Issue Type: New Feature
>Reporter: hong hyungseok
>
> When hadoop installed on aws, 
> S3 storage can be used as hdfs filesystem.
> But, Sentry doesn't support S3 synchronization as it did with hdfs.



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

[jira] [Comment Edited] (SENTRY-1457) DB, Table permission when connected with S3 storage on aws

[Anne Yu (JIRA)]

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

Anne Yu edited comment on SENTRY-1457 at 9/3/16 1:53 AM:
-

Seems Amazon S3 starts to support ACLs, similar to HDFS Acls: 
http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html. It will be 
helpful to have it for Sentry + HDFS Synced Extended ACLs.


was (Author: anneyu):
Seems Amazon S3 starts to support ACLs, similar to HDFS Acls: 
http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html. It will be 
helpful to have it feature for Sentry + HDFS Synced Extended ACLs.

> DB, Table permission when connected with S3 storage on aws
> --
>
> Key: SENTRY-1457
> URL: https://issues.apache.org/jira/browse/SENTRY-1457
> Project: Sentry
>  Issue Type: New Feature
>Reporter: hong hyungseok
>
> When hadoop installed on aws, 
> S3 storage can be used as hdfs filesystem.
> But, Sentry doesn't support S3 synchronization as it did with hdfs.



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

[jira] [Updated] (SENTRY-1456) SENTRY-1454 follow up: Commit message and rat check failure

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1456:

   Resolution: Fixed
Fix Version/s: 1.8.0
   Status: Resolved  (was: Patch Available)

> SENTRY-1454 follow up: Commit message and rat check failure
> ---
>
> Key: SENTRY-1456
> URL: https://issues.apache.org/jira/browse/SENTRY-1456
> Project: Sentry
>  Issue Type: Task
>Affects Versions: 1.8.0
>Reporter: Sravya Tirukkovalur
>Assignee: Anne Yu
>Priority: Blocker
> Fix For: 1.8.0
>
> Attachments: SENTRY-1454.0.patch
>
>
> Current commit message is inaccurate:
> "SENTRY-1429, SENTRY-1455: fix flaky TestHDFSIntegration, refactor this huge 
> test class, improve its cleanUp and setUp for temp HDFS dirs; divide test 
> class into smoke test class and p2 test class; in post commit run, we will 
> only run smoke tests."
> Seems like it should just be 
> "SENTRY-1454:Fix intermittent time out issue for TestHDFSIntegration
> " 
> -  SENTRY-1429 is the uber jira, but we do not have to mention it in the 
> commit description. Can be added to extended description if needed.
> - SENTRY-1455 seems not related?
> Also, a new file TestHDFSIntegrationEnd2End.java does not seem to have 
> license header. This needs to be fixed.



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

[jira] [Updated] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1454:

   Resolution: Fixed
Fix Version/s: 1.8.0
   Status: Resolved  (was: Patch Available)

commit 5cfd82d96e9baef51f7291d48e717c922baf2224
Author: Anne Yu 
Date:   Fri Aug 26 17:04:19 2016 -0700

SENTRY-1429, SENTRY-1455: fix flaky TestHDFSIntegration, refactor this huge 
test class, improve its cleanUp and setUp for temp HDFS dirs; divide test class 
into smoke test class and p2 test class; in post commit run, we will only run 
smoke tests.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch, SENTRY-1429.4.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Comment Edited] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

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

Anne Yu edited comment on SENTRY-1454 at 8/29/16 8:06 PM:
--

Transferred code review ship-it to +1.


was (Author: anneyu):
For all unit tests issues existing in the trunck, here are the plan:

1. Lets get Anne's fix in asap
2. Unblock post commit
3. If there are still failures, disable the problematic ones and continue 
investigation.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Commented] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1454:
-

For all unit tests issues existing in the trunck, here are the plan:

1. Lets get Anne's fix in asap
2. Unblock post commit
3. If there are still failures, disable the problematic ones and continue 
investigation.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Commented] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1454:
-

Thank you, [~sravya] and [~hahao] for the code review. Seems we agreed to 
check-in.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1454:

Attachment: SENTRY-1429.3.patch

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch, SENTRY-1429.1.patch, 
> SENTRY-1429.3.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Commented] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1454:
-

Yeah, but it's difficult to combine these two from this particular jira. I am 
thinking of checking in this one to unblock post commit then rebase 
SENTRY-1377, which can happen anytime later, in a more flexible schedule. The 
main purpose for this jira is to ensure no time out. Refactor can continue 
going on.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1454:

Attachment: SENTRY-1429.0.patch

[~sravya] and [~hahao], please help take a look. It attempts to fix 
TestHDFSIntegration flaky tests and also unblock post commit job by turning off 
flaky solr tests.

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1429.0.patch
>
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1454:

Status: Patch Available  (was: Open)

> Fix intermittent time out issue for TestHDFSIntegration
> ---
>
> Key: SENTRY-1454
> URL: https://issues.apache.org/jira/browse/SENTRY-1454
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> Occasionally there are time out issues from TestHDFSIntegration. It turns out 
> it contains 45 test functions and runs over 10m. Need to split the tests into 
> smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1429) TestHDFSIntegration improvements

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1429:

Affects Version/s: 1.8.0
   Status: Patch Available  (was: Open)

> TestHDFSIntegration improvements
> 
>
> Key: SENTRY-1429
> URL: https://issues.apache.org/jira/browse/SENTRY-1429
> Project: Sentry
>  Issue Type: Test
>Affects Versions: 1.8.0
>Reporter: Sravya Tirukkovalur
>Assignee: Anne Yu
>
> There are a few problems with this test that would be good to fix:
> 1. NN pulls the Sentry acls periodically, which means tests cannot verify 
> acls as soon as it sets up the required privileges. This requires having 
> sleeps in the test but it leads to some flakyness. We need to make sure we 
> are actually sleeping after setting the permissions and before veryfying. Or 
> explore other options to make this robust.
> 2. We need to make the tests more granular. There is a bunch of stuff 
> happening in a single test, so it is hard to pinpoint why a test failed 
> without looking at the stacktrace and debugging further.
> 3. Fix inter test dependencies if any. I see that some tests pass if run 
> alone, but fail when the entire test class is run, so there might be some 
> dependencies which we need to clean up.
> 4. Make these tests runnable on real cluster. So that we can catch any 
> integration and configuration issues.



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

[jira] [Created] (SENTRY-1454) Fix intermittent time out issue for TestHDFSIntegration

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1454:
---

 Summary: Fix intermittent time out issue for TestHDFSIntegration
 Key: SENTRY-1454
 URL: https://issues.apache.org/jira/browse/SENTRY-1454
 Project: Sentry
  Issue Type: Bug
  Components: Sentry
Affects Versions: 1.8.0
Reporter: Anne Yu
Assignee: Anne Yu


Occasionally there are time out issues from TestHDFSIntegration. It turns out 
it contains 45 test functions and runs over 10m. Need to split the tests into 
smaller size class file. And testAccessToTableDirectory sometimes if flaky.



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thank you [~hahao], 

commit 53dc2d6f41633b55711f0aff8d5e4c9be301255d
Author: Anne Yu 
Date:   Tue Aug 23 12:16:41 2016 -0700

SENTRY-1447: When s3 is configured as HDFS defaultFS and Hive Warehouse 
Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java. 
(Anne Yu, reviewed by Hao Hao).

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch, SENTRY-1447.1.patch, 
> SENTRY-1447.2.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Attachment: SENTRY-1447.2.patch

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch, SENTRY-1447.1.patch, 
> SENTRY-1447.2.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Attachment: (was: SENTRY-1447.2.patch)

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch, SENTRY-1447.1.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Attachment: SENTRY-1447.2.patch

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch, SENTRY-1447.1.patch, 
> SENTRY-1447.2.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Commented] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1447:
-

TestColumnEndToEnd.java times out frequently after fix the test.

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch, SENTRY-1447.1.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Resolved] (SENTRY-1250) Document kafka integration with sentry

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu resolved SENTRY-1250.
-
Resolution: Fixed

Doc is posted in the upstream wiki. Thanks Ashish!

> Document kafka integration with sentry
> --
>
> Key: SENTRY-1250
> URL: https://issues.apache.org/jira/browse/SENTRY-1250
> Project: Sentry
>  Issue Type: Bug
>  Components: kafka-integration, Sentry
>Affects Versions: 1.7.0
>Reporter: Anne Yu
>Assignee: Ashish K Singh
>  Labels: Docs
>
> [~singhashish] could it be possible to finish this 
> [doc|https://cwiki.apache.org/confluence/display/SENTRY/%5BWIP%5DKafka+Authorization+via+Sentry]?
>  Thanks.



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

[jira] [Updated] (SENTRY-1250) Document kafka integration with sentry

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1250:

Fix Version/s: 1.8.0

> Document kafka integration with sentry
> --
>
> Key: SENTRY-1250
> URL: https://issues.apache.org/jira/browse/SENTRY-1250
> Project: Sentry
>  Issue Type: Bug
>  Components: kafka-integration, Sentry
>Affects Versions: 1.7.0
>Reporter: Anne Yu
>Assignee: Ashish K Singh
>  Labels: Docs
> Fix For: 1.8.0
>
>
> [~singhashish] could it be possible to finish this 
> [doc|https://cwiki.apache.org/confluence/display/SENTRY/%5BWIP%5DKafka+Authorization+via+Sentry]?
>  Thanks.



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

[jira] [Assigned] (SENTRY-1250) Document kafka integration with sentry

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu reassigned SENTRY-1250:
---

Assignee: Ashish K Singh

> Document kafka integration with sentry
> --
>
> Key: SENTRY-1250
> URL: https://issues.apache.org/jira/browse/SENTRY-1250
> Project: Sentry
>  Issue Type: Bug
>  Components: kafka-integration, Sentry
>Affects Versions: 1.7.0
>Reporter: Anne Yu
>Assignee: Ashish K Singh
>  Labels: Docs
>
> [~singhashish] could it be possible to finish this 
> [doc|https://cwiki.apache.org/confluence/display/SENTRY/%5BWIP%5DKafka+Authorization+via+Sentry]?
>  Thanks.



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Attachment: SENTRY-1447.0.patch

> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
> Attachments: SENTRY-1447.0.patch
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Description: 
org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme

  was:
org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme
org.apache.sentry.tests.e2e.dbprovider.TestColumnEndToEnd.testCrossDbTableOperations
org.apache.sentry.tests.e2e.dbprovider.TestDbSandboxOps.testInsertOverwriteAndLoadData


> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Updated] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1447:

Description: 
org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme


  was:
org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme
org.apache.sentry.tests.e2e.dbprovider.TestColumnEndToEnd.testCrossDbTableOperations
org.apache.sentry.tests.e2e.dbprovider.TestDbSandboxOps.testInsertOverwriteAndLoadData


> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme



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

[jira] [Commented] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1447:
-

org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups need to be ignored for 
Sentry on S3;

If run 
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable, 
have to correctly configure "-Dsentry.e2etest.storage.uri=s3a://sentry-s3";

Add exec(statement, "set hive.exim.uri.scheme.whitelist=hdfs,pfile,s3a;"); for 
import/export tests;







> When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix 
> some e2e test failures. For example, TestDbHdfsMaxGroups.java.
> --
>
> Key: SENTRY-1447
> URL: https://issues.apache.org/jira/browse/SENTRY-1447
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
>
> org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
> org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
> org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
> org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
> org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme
> org.apache.sentry.tests.e2e.dbprovider.TestColumnEndToEnd.testCrossDbTableOperations
> org.apache.sentry.tests.e2e.dbprovider.TestDbSandboxOps.testInsertOverwriteAndLoadData



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

[jira] [Created] (SENTRY-1447) When s3 is configured as HDFS defaultFS and Hive Warehouse Dir, need to fix some e2e test failures. For example, TestDbHdfsMaxGroups.java.

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1447:
---

 Summary: When s3 is configured as HDFS defaultFS and Hive 
Warehouse Dir, need to fix some e2e test failures. For example, 
TestDbHdfsMaxGroups.java.
 Key: SENTRY-1447
 URL: https://issues.apache.org/jira/browse/SENTRY-1447
 Project: Sentry
  Issue Type: Bug
  Components: Sentry
Affects Versions: 1.8.0
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: 1.8.0


org.apache.sentry.tests.e2e.dbprovider.TestDbExportImportPrivileges.testExportImportPrivileges
org.apache.sentry.tests.e2e.dbprovider.TestDbOperationsPart2.testExportImport
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsExtMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroups
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntDbTblMaxAclsWithGroupsNoPar
org.apache.sentry.tests.e2e.hdfs.TestDbHdfsMaxGroups.testIntColMaxAclsWithGroups
org.apache.sentry.tests.e2e.hive.fs.TestHiveWarehouseOnExtFs.TestCreateTable
org.apache.sentry.tests.e2e.hive.fs.TestTableOnExtFS.TestCreateExtTableWithoutScheme
org.apache.sentry.tests.e2e.dbprovider.TestColumnEndToEnd.testCrossDbTableOperations
org.apache.sentry.tests.e2e.dbprovider.TestDbSandboxOps.testInsertOverwriteAndLoadData



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

[jira] [Created] (SENTRY-1446) Upgrade httpmime (Sentry) to 4.3.6 or greater.

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1446:
---

 Summary: Upgrade httpmime (Sentry) to 4.3.6 or greater.
 Key: SENTRY-1446
 URL: https://issues.apache.org/jira/browse/SENTRY-1446
 Project: Sentry
  Issue Type: New Feature
  Components: Sentry
Affects Versions: 1.8.0
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: 1.8.0


http/conn/ssl/SSLConnectionSocketFactory.java in Apache HttpComponents 
HttpClient before 4.3.6 ignores the http.socket.timeout configuration setting 
during an SSL handshake, which allows remote attackers to cause a denial of 
service (HTTPS call hang) via unspecified vectors.
Upgrade to 4.3.6 or greater.



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

[jira] [Updated] (SENTRY-1406) Refactor: move AuthorizationProvider out of sentry-provider-common

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1406:

Affects Version/s: 1.8.0
Fix Version/s: 1.8.0

> Refactor: move AuthorizationProvider out of sentry-provider-common
> --
>
> Key: SENTRY-1406
> URL: https://issues.apache.org/jira/browse/SENTRY-1406
> Project: Sentry
>  Issue Type: Improvement
>  Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Colin Ma
>Assignee: Colin Ma
> Fix For: 1.8.0
>
> Attachments: SENTRY-1406.001.patch, SENTRY-1406.002.patch, 
> SENTRY-1406.003.patch
>
>
> Currently, both AuthorizationProvider and ProviderBackend are in 
> sentry-provider-common. It'll cause the circle dependency problem. Create a 
> new module(eg, sentry-authorization-provider), and move AuthorizationProvider 
> to this new module.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: SENTRY-1423.3-sentry-ha-redesign.patch

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, 
> SENTRY-1423.2-sentry-ha-redesign.patch, SENTRY-1423.3-sentry-ha-redesign.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: SENTRY-1423.2-sentry-ha-redesign.patch

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, 
> SENTRY-1423.2-sentry-ha-redesign.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Commented] (SENTRY-1404) Use the new INodeAttributesProvider API in sentry-hdfs

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1404:
-

+1 upon successful run of hadoop-qa.

> Use the new INodeAttributesProvider API in sentry-hdfs
> --
>
> Key: SENTRY-1404
> URL: https://issues.apache.org/jira/browse/SENTRY-1404
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Colin P. McCabe
>Assignee: Hao Hao
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1404.0.patch, 
> SENTRY-1404.001-sentry-ha-redesign.patch, SENTRY-1404.1.patch, 
> SENTRY-1404.2.patch
>
>
> Use the new INodeAttributesProvider API in sentry-hdfs



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

[jira] [Commented] (SENTRY-1404) Use the new INodeAttributesProvider API in sentry-hdfs

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1404:
-

+1. Seems the failure is irrelevant. Thanks for you patch!

> Use the new INodeAttributesProvider API in sentry-hdfs
> --
>
> Key: SENTRY-1404
> URL: https://issues.apache.org/jira/browse/SENTRY-1404
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Colin P. McCabe
>Assignee: Hao Hao
> Fix For: 1.8.0, sentry-ha-redesign
>
> Attachments: SENTRY-1404.0.patch, 
> SENTRY-1404.001-sentry-ha-redesign.patch, SENTRY-1404.1.patch
>
>
> Use the new INodeAttributesProvider API in sentry-hdfs



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: (was: SENTRY-1423.0.patch)

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0-sentry-ha-redesign.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: SENTRY-1423.0-sentry-ha-redesign.patch

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, 
> SENTRY-1423.0.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: SENTRY-1423.0.patch

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: (was: SENTRY-1423.0.patch)

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Attachment: SENTRY-1423.0.patch

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1423.0.patch
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Updated] (SENTRY-1415) [Test hook] Provide a hook to stop the active sentry sevice

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1415:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thanks [~rahul9269].

commit 39c473c1f47ae73a131bc3ab607d4400a4aabe54
Author: Anne Yu 
Date:   Thu Jul 28 15:11:59 2016 -0700

SENTRY-1415: Provide a hook to stop the active sentry sevice. (Rahul 
Sharma, reviewed by Anne Yu).


> [Test hook] Provide a hook to stop the active sentry sevice
> ---
>
> Key: SENTRY-1415
> URL: https://issues.apache.org/jira/browse/SENTRY-1415
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Reporter: Sravya Tirukkovalur
>Assignee: Rahul Sharma
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1415.0-sentry-ha-redesign.patch, 
> SENTRY-1415.1-sentry-ha-redesign.patch
>
>
> This would be required for writing e2e tests in junit to test failover.



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

[jira] [Commented] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1423:
-

Also validate during failover correct sentry exception will be thrown.

> Sentry HA Test: programmatic failover in a mini cluster env; also add some 
> test data.
> -
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Created] (SENTRY-1430) Test Sentry HA Tasks

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1430:
---

 Summary: Test Sentry HA Tasks 
 Key: SENTRY-1430
 URL: https://issues.apache.org/jira/browse/SENTRY-1430
 Project: Sentry
  Issue Type: Sub-task
  Components: Sentry
Affects Versions: sentry-ha-redesign
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: sentry-ha-redesign


A Uber jira to capture all sentry ha test automation tasks.



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

[jira] [Updated] (SENTRY-1424) Sentry HA client tests: ensure connect to active and block from passive

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1424:

Summary: Sentry HA client tests: ensure connect to active and block from 
passive  (was: Sentry ha client tests: ensure connect to active and block from 
passive)

> Sentry HA client tests: ensure connect to active and block from passive
> ---
>
> Key: SENTRY-1424
> URL: https://issues.apache.org/jira/browse/SENTRY-1424
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> 1. client can connect to active;
> 2. client can't connect to passive;
> 3. multiple clients can connect to active;



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

[jira] [Assigned] (SENTRY-1429) Refactor TestHDFSIntegration

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu reassigned SENTRY-1429:
---

Assignee: Anne Yu

> Refactor TestHDFSIntegration
> 
>
> Key: SENTRY-1429
> URL: https://issues.apache.org/jira/browse/SENTRY-1429
> Project: Sentry
>  Issue Type: Test
>Reporter: Sravya Tirukkovalur
>Assignee: Anne Yu
>
> There are a few problems with this test that would be good to fix:
> 1. NN pulls the Sentry acls periodically, which means tests cannot verify 
> acls as soon as it sets up the required privileges. This requires having 
> sleeps in the test but it leads to some flakyness. We need to make sure we 
> are actually sleeping after setting the permissions and before veryfing. Or 
> explore other options to make this robust.
> 2. We need to make the tests more granular. There is a bunch of stuff 
> happening in a single test, so it is hard to pinpoint why a test failed 
> without looking at the stacktrace and debugging further.
> 3. Fix inter test dependencies if any. I see that some tests fail if run 
> alone, but fail when the entire test class is run, so there might be some 
> depedencies which we need to clean up.
> 4. Make these tests runnable on real cluster. So that we can catch any 
> integration and configuration issues.



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

[jira] [Updated] (SENTRY-1423) test programmatic failover in a mini cluster env; also add some test data.

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1423:

Summary: test programmatic failover in a mini cluster env; also add some 
test data.  (was: test programmatic failover in a minicluster env; also add 
some data also)

> test programmatic failover in a mini cluster env; also add some test data.
> --
>
> Key: SENTRY-1423
> URL: https://issues.apache.org/jira/browse/SENTRY-1423
> Project: Sentry
>  Issue Type: Bug
>  Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: sentry-ha-redesign
>
>
> .create role, grant privileges
> .failover
> .validate role and privileges.



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

[jira] [Assigned] (SENTRY-1424) Sentry ha client tests: ensure connect to active and block from passive

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu reassigned SENTRY-1424:
---

Assignee: Anne Yu

> Sentry ha client tests: ensure connect to active and block from passive
> ---
>
> Key: SENTRY-1424
> URL: https://issues.apache.org/jira/browse/SENTRY-1424
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
>
> 1. client can connect to active;
> 2. client can't connect to passive;
> 3. multiple clients can connect to active;



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

[jira] [Created] (SENTRY-1424) Sentry ha client tests: ensure connect to active and block from passive

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1424:
---

 Summary: Sentry ha client tests: ensure connect to active and 
block from passive
 Key: SENTRY-1424
 URL: https://issues.apache.org/jira/browse/SENTRY-1424
 Project: Sentry
  Issue Type: Bug
Reporter: Anne Yu


1. client can connect to active;
2. client can't connect to passive;
3. multiple clients can connect to active;



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

[jira] [Created] (SENTRY-1423) test programmatic failover in a minicluster env; also add some data also

[Anne Yu (JIRA)]

Anne Yu created SENTRY-1423:
---

 Summary: test programmatic failover in a minicluster env; also add 
some data also
 Key: SENTRY-1423
 URL: https://issues.apache.org/jira/browse/SENTRY-1423
 Project: Sentry
  Issue Type: Bug
  Components: Sentry
Affects Versions: sentry-ha-redesign
Reporter: Anne Yu
Assignee: Anne Yu
 Fix For: sentry-ha-redesign


.create role, grant privileges
.failover
.validate role and privileges.



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

[jira] [Commented] (SENTRY-1331) Add a kerberos end to end test case to access isActive and isHa metrics.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1331:
-

Thanks [~rahul9269] for your patch. +1. It will be nice to have a following 
test case basically is the same but with sentry HA enabled. The intention is to 
ensure isHA can correctly exposed master server.


> Add a kerberos end to end test case to access isActive and isHa metrics.
> 
>
> Key: SENTRY-1331
> URL: https://issues.apache.org/jira/browse/SENTRY-1331
> Project: Sentry
>  Issue Type: Bug
>  Components: Hdfs Plugin
>Affects Versions: 1.8.0
>Reporter: Rahul Sharma
>Assignee: Rahul Sharma
> Attachments: SENTRY-1331.1.sentry-ha-redesign.patch, 
> SENTRY-1331.2.sentry-ha-redesign.patch, SENTRY-1331.3-sentry-ha-redesign.patch
>
>
> Add a kerberos end to end test case to access isActive and isHa metrics.
> This is a follow on jira for SENTRY-1319



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

[jira] [Commented] (SENTRY-848) [column level privilege] if grant user column level select privilege, DESCRIBE FORMATTED table[.column] shouldn't require extra table level privilege

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-848:


In that saying, maybe we don't need this patch checked in for now. But 
definitely when situation changes, we can revisit. Keep this bug open.

> [column level privilege] if grant user column level select privilege, 
> DESCRIBE FORMATTED table[.column] shouldn't require extra table level 
> privilege
> -
>
> Key: SENTRY-848
> URL: https://issues.apache.org/jira/browse/SENTRY-848
> Project: Sentry
>  Issue Type: Bug
>Affects Versions: 1.5.1
>Reporter: Anne Yu
>Assignee: Ke Jia
> Attachments: SENTRY-848-001.patch, SENTRY-848-002.patch, 
> SENTRY-848-002.patch, SENTRY-848-003.patch
>
>
> {code}
> create table test_tb(s string, i int);
> grant select(s) on table test_tb to role test_role;
> grant role test_role to group test_user;
> {code}
> use test_user to login,
> {code}
> describe formatted test_tb s;
> Error: Error while compiling statement: FAILED: SemanticException No valid 
> privileges
>  Required privileges for this query: 
> Server=server1->Db=test_db->Table=test_tb->action=insert;Server=server1->Db=test_db->Table=test_tb->action=select;
>  (state=42000,code=4)
> {code}
> How about describe [formatted] test_tb; do we allow test_user to list his 
> permitted columns? for example,
> +---++--+--+
> | col_name  | data_type  | comment  |
> +---++--+--+
> | s | string |  |
> +---++--+--+
> 2 rows selected (0.167 seconds)
> However "ANALYZE TABLE test_tb COMPUTE STATISTICS FOR COLUMNS s" is allowed 
> for test_user.



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

[jira] [Commented] (SENTRY-848) [column level privilege] if grant user column level select privilege, DESCRIBE FORMATTED table[.column] shouldn't require extra table level privilege

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-848:


FYI, [~lskuff] confirmed the behavior could be best for our current users:
{code}
Allow (If user has access to any column in the table):
Basic DESCRIBE TABLE and SHOW COLUMNS. Blocking these is a usability issue and 
impacts Hue integration.
Note: Do not filter column values. May revisit this in the future.
Block (Require Table-Level Privileges):
DESCRIBE FORMATTED/DESCRIBE EXTENDED
SHOW COLUMN STATS
SHOW PARTITIONS
COMPUTE STATS/ANALYZE TABLE
It seems like there is a bug with ANALYZE TABLE, but I'm not sure we want to 
change the behavior for DESCRIBE EXTENDED. Especially since this can expose 
information about views.
{code}

> [column level privilege] if grant user column level select privilege, 
> DESCRIBE FORMATTED table[.column] shouldn't require extra table level 
> privilege
> -
>
> Key: SENTRY-848
> URL: https://issues.apache.org/jira/browse/SENTRY-848
> Project: Sentry
>  Issue Type: Bug
>Affects Versions: 1.5.1
>Reporter: Anne Yu
>Assignee: Ke Jia
> Attachments: SENTRY-848-001.patch, SENTRY-848-002.patch, 
> SENTRY-848-002.patch, SENTRY-848-003.patch
>
>
> {code}
> create table test_tb(s string, i int);
> grant select(s) on table test_tb to role test_role;
> grant role test_role to group test_user;
> {code}
> use test_user to login,
> {code}
> describe formatted test_tb s;
> Error: Error while compiling statement: FAILED: SemanticException No valid 
> privileges
>  Required privileges for this query: 
> Server=server1->Db=test_db->Table=test_tb->action=insert;Server=server1->Db=test_db->Table=test_tb->action=select;
>  (state=42000,code=4)
> {code}
> How about describe [formatted] test_tb; do we allow test_user to list his 
> permitted columns? for example,
> +---++--+--+
> | col_name  | data_type  | comment  |
> +---++--+--+
> | s | string |  |
> +---++--+--+
> 2 rows selected (0.167 seconds)
> However "ANALYZE TABLE test_tb COMPUTE STATISTICS FOR COLUMNS s" is allowed 
> for test_user.



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

[jira] [Commented] (SENTRY-1331) Add a kerberos end to end test case to access isActive and isHa metrics.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1331:
-

Thank you [~rahul9269], left some comments on your cr.

> Add a kerberos end to end test case to access isActive and isHa metrics.
> 
>
> Key: SENTRY-1331
> URL: https://issues.apache.org/jira/browse/SENTRY-1331
> Project: Sentry
>  Issue Type: Bug
>  Components: Hdfs Plugin
>Affects Versions: 1.8.0
>Reporter: Rahul Sharma
>Assignee: Rahul Sharma
> Attachments: SENTRY-1331.1.sentry-ha-redesign.patch
>
>
> Add a kerberos end to end test case to access isActive and isHa metrics.
> This is a follow on jira for SENTRY-1319



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

[jira] [Resolved] (SENTRY-1410) Enable sentry ha, validate is able to read active sentry server

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu resolved SENTRY-1410.
-
   Resolution: Duplicate
Fix Version/s: 1.8.0

> Enable sentry ha, validate is able to read active sentry server
> ---
>
> Key: SENTRY-1410
> URL: https://issues.apache.org/jira/browse/SENTRY-1410
> Project: Sentry
>  Issue Type: Bug
>Reporter: Anne Yu
>Assignee: Anne Yu
> Fix For: 1.8.0
>
>
> See SENTRY-1319, add test case when enable sentry ha, active is able to read.



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

[jira] [Commented] (SENTRY-1331) Add a kerberos end to end test case to access isActive and isHa metrics.

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1331:
-

Thanks [~rahul.9269], could you add a rb link?

> Add a kerberos end to end test case to access isActive and isHa metrics.
> 
>
> Key: SENTRY-1331
> URL: https://issues.apache.org/jira/browse/SENTRY-1331
> Project: Sentry
>  Issue Type: Bug
>  Components: Hdfs Plugin
>Affects Versions: 1.8.0
>Reporter: Rahul Sharma
>Assignee: Rahul Sharma
> Attachments: SENTRY-1331.1.sentry-ha-redesign.patch
>
>
> Add a kerberos end to end test case to access isActive and isHa metrics.
> This is a follow on jira for SENTRY-1319



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

[jira] [Commented] (SENTRY-1399) Integrate Fencer with SentryStore

[Anne Yu (JIRA)]

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

Anne Yu commented on SENTRY-1399:
-

+1. Thanks [~cmccabe].

> Integrate Fencer with SentryStore
> -
>
> Key: SENTRY-1399
> URL: https://issues.apache.org/jira/browse/SENTRY-1399
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Colin P. McCabe
>Assignee: Colin P. McCabe
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1399.001-sentry-ha-redesign.patch, 
> SENTRY-1399.002-sentry-ha-redesign.patch, 
> SENTRY-1399.003-sentry-ha-redesign.patch
>
>
> Integrate Fencer with the SentryStore.  Add more unit tests



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

[jira] [Updated] (SENTRY-1399) Integrate Fencer with SentryStore

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1399:

Attachment: SENTRY-1399.003-sentry-ha-redesign.patch

Just resubmitted the same patch as 002 to re-trigger hadoop-qa.

> Integrate Fencer with SentryStore
> -
>
> Key: SENTRY-1399
> URL: https://issues.apache.org/jira/browse/SENTRY-1399
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Colin P. McCabe
>Assignee: Colin P. McCabe
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1399.001-sentry-ha-redesign.patch, 
> SENTRY-1399.002-sentry-ha-redesign.patch, 
> SENTRY-1399.003-sentry-ha-redesign.patch
>
>
> Integrate Fencer with the SentryStore.  Add more unit tests



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

[jira] [Updated] (SENTRY-1398) Fix TestLeaderStatus#testRacingClients

[Anne Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SENTRY-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anne Yu updated SENTRY-1398:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

commit 6f298b0f71efb9c26ee21ea27a514b4ebca02cd8
Author: Anne Yu 
Date:   Thu Jul 14 11:52:36 2016 -0700

SENTRY-1398: Fix TestLeaderStatus#testRacingClients time out issue. ( Colin 
P. McCabe, reviewed by Anne Yu)

> Fix TestLeaderStatus#testRacingClients
> --
>
> Key: SENTRY-1398
> URL: https://issues.apache.org/jira/browse/SENTRY-1398
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Core
>Affects Versions: sentry-ha-redesign
>Reporter: Colin P. McCabe
>Assignee: Colin P. McCabe
>Priority: Minor
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1398.001-sentry-ha-redesign.patch, 
> SENTRY-1398.002-sentry-ha-redesign.patch, 
> SENTRY-1398.003-sentry-ha-redesign.patch, 
> SENTRY-1398.004-sentry-ha-redesign.patch
>
>
> TestLeaderStatus#testRacingClients has been hanging on Jenkins, although not 
> locally.



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