[jira] [Updated] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1844: --- Resolution: Fixed Fix Version/s: 1.8.0 Status: Resolved (was: Patch Available) Committed to master. Thank [~davidxdh] for the contribution. commit b6239b2bad38399d356f3dccb703e4d80250bdb2 Author: Donghui XuDate: Mon Jul 24 15:21:12 2017 +0800 SENTRY-1844 - When setting web authentication type to none, sentry fails to start - Reviewed by: Dapeng Sun. > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu > Fix For: 1.8.0 > > Attachments: SENTRY-1844.001.patch, SENTRY-1844.002.patch, > SENTRY-1844.003.patch, SENTRY-1844.004.patch, SENTRY-1844.005.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098038#comment-16098038 ] Dapeng Sun commented on SENTRY-1836: Committed to master. Thank [~davidxdh] for the contribution. commit b7a952cac04fb87cf58c91ed8fe421beb3daa43d Author: Donghui XuDate: Mon Jul 24 15:25:35 2017 +0800 SENTRY-1836 - Add sentry web service config in service template - Reviewed by: Dapeng Sun. > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.7.0 >Reporter: Donghui Xu >Assignee: Donghui Xu >Priority: Minor > Fix For: 1.8.0 > > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1836: --- Affects Version/s: 1.7.0 > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.7.0 >Reporter: Donghui Xu >Assignee: Donghui Xu >Priority: Minor > Fix For: 1.8.0 > > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1836: --- Resolution: Fixed Fix Version/s: 1.8.0 Status: Resolved (was: Patch Available) > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu >Priority: Minor > Fix For: 1.8.0 > > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091176#comment-16091176 ] Dapeng Sun commented on SENTRY-1836: Hi [~davidxdh], after the patch is committed, I will mark the jira as resolved and add a fixed version. After the fixed version is released, the release manager would close it. > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu >Priority: Minor > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091113#comment-16091113 ] Dapeng Sun commented on SENTRY-1844: +1 > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu > Attachments: SENTRY-1844.001.patch, SENTRY-1844.002.patch, > SENTRY-1844.003.patch, SENTRY-1844.004.patch, SENTRY-1844.005.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089269#comment-16089269 ] Dapeng Sun commented on SENTRY-1844: Thank [~davidxdh], the patch may miss some imports. Could you fix them? > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu > Attachments: SENTRY-1844.001.patch, SENTRY-1844.002.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun reassigned SENTRY-1836: -- Assignee: Donghui Xu > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu >Priority: Minor > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun reassigned SENTRY-1844: -- Assignee: Donghui Xu > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu >Assignee: Donghui Xu > Attachments: SENTRY-1844.001.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089238#comment-16089238 ] Dapeng Sun commented on SENTRY-1836: Thank [~davidxdh], let's wait one working day, I will commit it to master if there are no comments from other committers. > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Donghui Xu >Priority: Minor > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch, > SENTRY-1836.003.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089230#comment-16089230 ] Dapeng Sun commented on SENTRY-1844: [~davidxdh], for your reference: https://github.com/apache/sentry/blob/master/sentry-service/sentry-service-server/src/test/java/org/apache/sentry/provider/db/service/thrift/TestSentryWebServerWithKerberos.java https://github.com/apache/sentry/blob/master/sentry-service/sentry-service-server/src/test/java/org/apache/sentry/provider/db/service/thrift/TestSentryWebServerWithoutSecurity.java > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu > Attachments: SENTRY-1844.001.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1844) When setting web authentication type to none, sentry fails to start
[ https://issues.apache.org/jira/browse/SENTRY-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089228#comment-16089228 ] Dapeng Sun commented on SENTRY-1844: Hi [~davidxdh], the fix looks good, please add a Unit Test for this issue. Thanks! > When setting web authentication type to none, sentry fails to start > --- > > Key: SENTRY-1844 > URL: https://issues.apache.org/jira/browse/SENTRY-1844 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Donghui Xu > Attachments: SENTRY-1844.001.patch > > > When setting web authentication type to none, sentry fails to start. Because > sentry can not recognize none value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1836) Add sentry web service config in service template
[ https://issues.apache.org/jira/browse/SENTRY-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089225#comment-16089225 ] Dapeng Sun commented on SENTRY-1836: Hi [~davidxdh], Thank you for the contribution. please fix {{152 }}: remove the blank, I'm +1 for the patch. > Add sentry web service config in service template > - > > Key: SENTRY-1836 > URL: https://issues.apache.org/jira/browse/SENTRY-1836 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Donghui Xu >Priority: Minor > Attachments: SENTRY-1836.001.patch, SENTRY-1836.002.patch > > > sentry has web service which is disabled by default. If the user wants to > enable this feature, but do not know how to configure. In order to facilitate > the user to enable this feature, relevant configuration items must be added > to the service template. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1512) Refactor the database transaction management
[ https://issues.apache.org/jira/browse/SENTRY-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624037#comment-15624037 ] Dapeng Sun commented on SENTRY-1512: Thank Colin for the contribution. Append the commit log. SENTRY-1512: Refactor the database transaction management (Colin Ma, reviewed by Alexander Kolbasov, Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/844b0372 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/844b0372 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/844b0372 Branch: refs/heads/master Commit: 844b037223ab8e3d73dcdaa8b919296424a79ebd Parents: b124675 Author: Colin MaAuthored: Tue Nov 1 10:07:05 2016 +0800 Committer: Colin Ma Committed: Tue Nov 1 10:07:05 2016 +0800 > Refactor the database transaction management > > > Key: SENTRY-1512 > URL: https://issues.apache.org/jira/browse/SENTRY-1512 > Project: Sentry > Issue Type: Improvement >Reporter: Colin Ma >Assignee: Colin Ma > Attachments: SENTRY-1512.001.patch > > > The update for SENTRY-1422 refactor the database transaction management, this > also should be ported to master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1512) Refactor the database transaction management
[ https://issues.apache.org/jira/browse/SENTRY-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15621386#comment-15621386 ] Dapeng Sun commented on SENTRY-1512: +1 > Refactor the database transaction management > > > Key: SENTRY-1512 > URL: https://issues.apache.org/jira/browse/SENTRY-1512 > Project: Sentry > Issue Type: Improvement >Reporter: Colin Ma >Assignee: Colin Ma > Attachments: SENTRY-1512.001.patch > > > The update for SENTRY-1422 refactor the database transaction management, this > also should be ported to master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1402) Add TestGrantUserToRole to V2
[ https://issues.apache.org/jira/browse/SENTRY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457254#comment-15457254 ] Dapeng Sun commented on SENTRY-1402: +1 > Add TestGrantUserToRole to V2 > - > > Key: SENTRY-1402 > URL: https://issues.apache.org/jira/browse/SENTRY-1402 > Project: Sentry > Issue Type: Test > Components: Hive V2 >Affects Versions: 1.8.0 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1402-001.patch > > > Add TestgrantUSerToRole.java to V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-1450) Have privilege converter set by Kafka binding
[ https://issues.apache.org/jira/browse/SENTRY-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434039#comment-15434039 ] Dapeng Sun edited comment on SENTRY-1450 at 8/24/16 1:44 AM: - Hi [~singhashish], the patch LGTM, I uploaded a patch with name {{SENTRY-1450.001.patch}} to trigger Jenkins was (Author: dapengsun): Hi [~singhashish], the patch LGTM, could you uploaded a patch with name {{SENTRY-1450.001.patch}} to trigger Jenkins? > Have privilege converter set by Kafka binding > -- > > Key: SENTRY-1450 > URL: https://issues.apache.org/jira/browse/SENTRY-1450 > Project: Sentry > Issue Type: Improvement >Reporter: Ashish K Singh >Assignee: Ashish K Singh > Attachments: SENTRY-1450.001.diff, SENTRY-1450.001.patch > > > Have privilege converter set by Kafka binding. This will avoid users from > having to specify one extra config, which as of now can only take one value > for Kafka plugin, when enabling caching. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1450) Have privilege converter set by Kafka binding
[ https://issues.apache.org/jira/browse/SENTRY-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434039#comment-15434039 ] Dapeng Sun commented on SENTRY-1450: Hi [~singhashish], the patch LGTM, could you uploaded a patch with name {{SENTRY-1450.001.patch}} to trigger Jenkins? > Have privilege converter set by Kafka binding > -- > > Key: SENTRY-1450 > URL: https://issues.apache.org/jira/browse/SENTRY-1450 > Project: Sentry > Issue Type: Improvement >Reporter: Ashish K Singh >Assignee: Ashish K Singh > Attachments: SENTRY-1450.001.diff > > > Have privilege converter set by Kafka binding. This will avoid users from > having to specify one extra config, which as of now can only take one value > for Kafka plugin, when enabling caching. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to 3 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceFailureCase Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1638/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12824053/SENTRY-996-002.patch against master. {color:red}Overall:{color} -1 due to 2 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1956/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to an error {color:red}ERROR:{color} failed to build with patch (exit code 1) Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1639/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to an error {color:red}ERROR:{color} mvn test exited 1 Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1649/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to an error {color:red}ERROR:{color} mvn test exited 1 Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1646/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to an error {color:red}ERROR:{color} mvn test exited 1 Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1630/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-996) Faulty loop logic in HdfsHAClientInvocationHandler + HAClientInvocationHandler
[ https://issues.apache.org/jira/browse/SENTRY-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-996: -- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12806107/SENTRY-996.001.patch against master. {color:red}Overall:{color} -1 due to an error {color:red}ERROR:{color} mvn test exited 1 Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1643/console This message is automatically generated.) > Faulty loop logic in HdfsHAClientInvocationHandler + > HAClientInvocationHandler > --- > > Key: SENTRY-996 > URL: https://issues.apache.org/jira/browse/SENTRY-996 > Project: Sentry > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Ke Jia > Attachments: SENTRY-996-002.patch, SENTRY-996.001.patch > > > As discussed on the review board here: https://reviews.apache.org/r/41349/ > Both the HdfsHAClientInvocationHandler + HAClientInvocationHandler contain a > while(true) loop that looks like it was designed to catch certain exceptions > + retry. However, the logic is faulty in that it will always return after the > first iteration, not matter what (as picked up by PMD). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1024) Document for Sentry Kafka integration
[ https://issues.apache.org/jira/browse/SENTRY-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425821#comment-15425821 ] Dapeng Sun commented on SENTRY-1024: Pretty good, thank [~singhashish] for the contribution. > Document for Sentry Kafka integration > - > > Key: SENTRY-1024 > URL: https://issues.apache.org/jira/browse/SENTRY-1024 > Project: Sentry > Issue Type: Sub-task >Affects Versions: 1.7.0 >Reporter: Dapeng Sun >Assignee: Ashish K Singh > Fix For: 1.8.0 > > > Documents for Sentry Kafka integration > https://cwiki.apache.org/confluence/display/SENTRY/Apache+Kafka+Authorization+with+Apache+Sentry -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1402) Add TestGrantUserToRole to V2
[ https://issues.apache.org/jira/browse/SENTRY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1402: --- Issue Type: Test (was: Bug) > Add TestGrantUserToRole to V2 > - > > Key: SENTRY-1402 > URL: https://issues.apache.org/jira/browse/SENTRY-1402 > Project: Sentry > Issue Type: Test > Components: Hive V2 >Affects Versions: 1.8.0 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1402-001.patch > > > Add TestgrantUSerToRole.java to V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1402) Add TestGrantUserToRole to V2
[ https://issues.apache.org/jira/browse/SENTRY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1402: --- Affects Version/s: 1.8.0 > Add TestGrantUserToRole to V2 > - > > Key: SENTRY-1402 > URL: https://issues.apache.org/jira/browse/SENTRY-1402 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Affects Versions: 1.8.0 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1402-001.patch > > > Add TestgrantUSerToRole.java to V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1402) Add TestGrantUserToRole to V2
[ https://issues.apache.org/jira/browse/SENTRY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1402: --- Summary: Add TestGrantUserToRole to V2 (was: Add TestgrantUSerToRole to V2) > Add TestGrantUserToRole to V2 > - > > Key: SENTRY-1402 > URL: https://issues.apache.org/jira/browse/SENTRY-1402 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Affects Versions: 1.8.0 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1402-001.patch > > > Add TestgrantUSerToRole.java to V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1402) Add TestgrantUSerToRole to V2
[ https://issues.apache.org/jira/browse/SENTRY-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1402: --- Summary: Add TestgrantUSerToRole to V2 (was: Add TestgrantUSerToRole.java to V2) > Add TestgrantUSerToRole to V2 > - > > Key: SENTRY-1402 > URL: https://issues.apache.org/jira/browse/SENTRY-1402 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Affects Versions: 1.8.0 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1402-001.patch > > > Add TestgrantUSerToRole.java to V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1406) Refactor: move AuthorizationProvider out of sentry-provider-common
[ https://issues.apache.org/jira/browse/SENTRY-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420609#comment-15420609 ] Dapeng Sun commented on SENTRY-1406: +1 > 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 >Reporter: Colin Ma >Assignee: Colin Ma > 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-1022) Document for Hive authorization V2
[ https://issues.apache.org/jira/browse/SENTRY-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1022: --- Assignee: Ke Jia (was: Dapeng Sun) Status: Patch Available (was: Open) Status update: Ke Jia have finished the inital document, it is under review by few people, please feel free to send email to Ke if you want to review it. > Document for Hive authorization V2 > -- > > Key: SENTRY-1022 > URL: https://issues.apache.org/jira/browse/SENTRY-1022 > Project: Sentry > Issue Type: Task >Reporter: Dapeng Sun >Assignee: Ke Jia > > A document for integrating Hive authorization V2 should be added to > https://cwiki.apache.org/confluence/display/SENTRY/Home -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1405) Add test for "show grant role on all " command in V2
[ https://issues.apache.org/jira/browse/SENTRY-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1405: --- Resolution: Fixed Status: Resolved (was: Patch Available) Repository: sentry Updated Branches: refs/heads/master 985f4ad59 -> ddae7c04e SENTRY-1405: Add test for "show grant role on all " command in V2 (Ke, Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/64fb094a Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/64fb094a Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/64fb094a > Add test for "show grant role on all " command in V2 > > > Key: SENTRY-1405 > URL: https://issues.apache.org/jira/browse/SENTRY-1405 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1405-001.patch > > > Add test for "show grant role on all " command in V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1438) Move PolicyFiles from sentry-provider-file to sentry-core-common in V2
[ https://issues.apache.org/jira/browse/SENTRY-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1438: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed, thank Ke. > Move PolicyFiles from sentry-provider-file to sentry-core-common in V2 > -- > > Key: SENTRY-1438 > URL: https://issues.apache.org/jira/browse/SENTRY-1438 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1438-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1438) Move PolicyFiles from sentry-provider-file to sentry-core-common in V2
[ https://issues.apache.org/jira/browse/SENTRY-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411199#comment-15411199 ] Dapeng Sun commented on SENTRY-1438: +1 > Move PolicyFiles from sentry-provider-file to sentry-core-common in V2 > -- > > Key: SENTRY-1438 > URL: https://issues.apache.org/jira/browse/SENTRY-1438 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1438-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1359) Implement SHOW ROLE GRANT USER user_name in V2
[ https://issues.apache.org/jira/browse/SENTRY-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405232#comment-15405232 ] Dapeng Sun commented on SENTRY-1359: +1 > Implement SHOW ROLE GRANT USER user_name in V2 > -- > > Key: SENTRY-1359 > URL: https://issues.apache.org/jira/browse/SENTRY-1359 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1359-001.patch, SENTRY-1359-002.patch, > SENTRY-1359-003.patch > > > Implement SHOW ROLE GRANT USER user_name in V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1405) Add test for "show grant role on all " command in V2
[ https://issues.apache.org/jira/browse/SENTRY-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405231#comment-15405231 ] Dapeng Sun commented on SENTRY-1405: +1 > Add test for "show grant role on all " command in V2 > > > Key: SENTRY-1405 > URL: https://issues.apache.org/jira/browse/SENTRY-1405 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1405-001.patch > > > Add test for "show grant role on all " command in V2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1357) SentryMetastorePostEventListenerBase.onAlterTable should check for null dereference
[ https://issues.apache.org/jira/browse/SENTRY-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1357: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1357: SentryMetastorePostEventListenerBase.onAlterTable should check for null dereference (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/29e5fd02 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/29e5fd02 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/29e5fd02 > SentryMetastorePostEventListenerBase.onAlterTable should check for null > dereference > --- > > Key: SENTRY-1357 > URL: https://issues.apache.org/jira/browse/SENTRY-1357 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1357-001.patch > > > SentryMetastorePostEventListenerBase.onAlterTable should check for null > dereference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to master SENTRY-1327: Enable show grant role roleName on all command (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/a53b20ad Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/a53b20ad Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/a53b20ad > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch, SENTRY-1327-004.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1134) Add user defined udf test case
[ https://issues.apache.org/jira/browse/SENTRY-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1134: --- Issue Type: Test (was: New Feature) > Add user defined udf test case > -- > > Key: SENTRY-1134 > URL: https://issues.apache.org/jira/browse/SENTRY-1134 > Project: Sentry > Issue Type: Test > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Anne Yu >Assignee: Ke Jia > Attachments: SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, > SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, SENTRY-1134-002.patch, > SENTRY-1134-004.patch, SENTRY-1134.003.patch > > > Add user defined UDF test, user create a jar then create udf from this jar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1094) SentryMetastorePostEventListener.onAlterTable should check for null dereference
[ https://issues.apache.org/jira/browse/SENTRY-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1094: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1094: SentryMetastorePostEventListener.onAlterTable should check for null dereference (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/7deefdb1 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/7deefdb1 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/7deefdb1 > SentryMetastorePostEventListener.onAlterTable should check for null > dereference > --- > > Key: SENTRY-1094 > URL: https://issues.apache.org/jira/browse/SENTRY-1094 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Hao Hao >Assignee: Ke Jia > Attachments: SENTRY-1094-001.patch, SENTRY-1094-002.patch, > SENTRY-1094-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1358) Implement Grant role_name To User user_name in V2
[ https://issues.apache.org/jira/browse/SENTRY-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1358: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1358: Implement Grant role_name To User user_name in V2 (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/c6c9fabb Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/c6c9fabb Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/c6c9fabb > Implement Grant role_name To User user_name in V2 > - > > Key: SENTRY-1358 > URL: https://issues.apache.org/jira/browse/SENTRY-1358 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1358-001.patch > > > Implement Grant role_name To User user_name in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1351) Enable alter table operation without outputs in V2
[ https://issues.apache.org/jira/browse/SENTRY-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1351: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1351: Enable alter table operation without outputs in V2 (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/a381e5bc Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/a381e5bc Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/a381e5bc > Enable alter table operation without outputs in V2 > --- > > Key: SENTRY-1351 > URL: https://issues.apache.org/jira/browse/SENTRY-1351 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1351-001.patch, SENTRY-1351-001.patch > > > Enable alter table operation without outputs in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1401) In V2, show role grant group groupname should not throw an exception if group doesnt exist in db.
[ https://issues.apache.org/jira/browse/SENTRY-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376199#comment-15376199 ] Dapeng Sun commented on SENTRY-1401: +1 > In V2, show role grant group groupname should not throw an exception if group > doesnt exist in db. > - > > Key: SENTRY-1401 > URL: https://issues.apache.org/jira/browse/SENTRY-1401 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1401-001.patch > > > In V2,show role grant group groupname should not throw an exception if group > doesnt exist in db. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-896) Restrict "Explain" Hive operation for table level privileges
[ https://issues.apache.org/jira/browse/SENTRY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372069#comment-15372069 ] Dapeng Sun commented on SENTRY-896: --- Yes, SENTRY-1396 will fix it. > Restrict "Explain" Hive operation for table level privileges > > > Key: SENTRY-896 > URL: https://issues.apache.org/jira/browse/SENTRY-896 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 1.8.0 > > Attachments: SENTRY-896.patch > > > This resolves part of Sentry-849, as it ensures users without atleast table > level privileges cannot do explain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1396) Restrict "Explain" Hive operation for table level privileges in V2
[ https://issues.apache.org/jira/browse/SENTRY-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1396: --- Summary: Restrict "Explain" Hive operation for table level privileges in V2 (was: Restrict "Explain" Hive operation for table level privileges in Value) > Restrict "Explain" Hive operation for table level privileges in V2 > -- > > Key: SENTRY-1396 > URL: https://issues.apache.org/jira/browse/SENTRY-1396 > Project: Sentry > Issue Type: Bug >Reporter: Dapeng Sun > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SENTRY-1396) Restrict "Explain" Hive operation for table level privileges in Value
Dapeng Sun created SENTRY-1396: -- Summary: Restrict "Explain" Hive operation for table level privileges in Value Key: SENTRY-1396 URL: https://issues.apache.org/jira/browse/SENTRY-1396 Project: Sentry Issue Type: Bug Reporter: Dapeng Sun -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1394) Fix compile error for sentry-test-hive-v2
[ https://issues.apache.org/jira/browse/SENTRY-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372041#comment-15372041 ] Dapeng Sun commented on SENTRY-1394: +1,thank Colin. > Fix compile error for sentry-test-hive-v2 > - > > Key: SENTRY-1394 > URL: https://issues.apache.org/jira/browse/SENTRY-1394 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Colin Ma >Assignee: Colin Ma > Attachments: SENTRY-1394.001-SENTRY-1205.patch > > > Update the import for the refactor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1354) add column level test cases for select ... group by, order by and where in V2
[ https://issues.apache.org/jira/browse/SENTRY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1354: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. SENTRY-1354: add column level test cases for select ... group by, order by and where in V2 (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/ef890217 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/ef890217 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/ef890217 > add column level test cases for select ... group by, order by and where in V2 > - > > Key: SENTRY-1354 > URL: https://issues.apache.org/jira/browse/SENTRY-1354 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1354-001.patch > > > add column level test cases for select ... group by, order by and where in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1349) Add permission check and test case for alter db set owner in V2
[ https://issues.apache.org/jira/browse/SENTRY-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1349: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1349: Add permission check and test case for alter db set owner in V2 (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/915b8024 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/915b8024 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/915b8024 > Add permission check and test case for alter db set owner in V2 > --- > > Key: SENTRY-1349 > URL: https://issues.apache.org/jira/browse/SENTRY-1349 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1349-001.patch, SENTRY-1349-001.patch > > > Add permission check and test case for alter db set owner in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1094) SentryMetastorePostEventListener.onAlterTable should check for null dereference
[ https://issues.apache.org/jira/browse/SENTRY-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360753#comment-15360753 ] Dapeng Sun commented on SENTRY-1094: Hi [~hahao], do you have any comments? > SentryMetastorePostEventListener.onAlterTable should check for null > dereference > --- > > Key: SENTRY-1094 > URL: https://issues.apache.org/jira/browse/SENTRY-1094 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Hao Hao >Assignee: Ke Jia > Attachments: SENTRY-1094-001.patch, SENTRY-1094-002.patch, > SENTRY-1094-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-320) show role grant group groupname should not throw an exception if group doesnt exist in db
[ https://issues.apache.org/jira/browse/SENTRY-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-320: -- Resolution: Fixed Status: Resolved (was: Patch Available) > show role grant group groupname should not throw an exception if group doesnt > exist in db > - > > Key: SENTRY-320 > URL: https://issues.apache.org/jira/browse/SENTRY-320 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Ke Jia > Fix For: 1.8.0 > > Attachments: SENTRY-320-001.patch, SENTRY-320-002.patch, > SENTRY-320-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-320) show role grant group groupname should not throw an exception if group doesnt exist in db
[ https://issues.apache.org/jira/browse/SENTRY-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360751#comment-15360751 ] Dapeng Sun commented on SENTRY-320: --- Committed to master, thank Ke SENTRY-320: show role grant group groupname should not throw an exception if group doesnt exist in db (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/528f34a8 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/528f34a8 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/528f34a8 > show role grant group groupname should not throw an exception if group doesnt > exist in db > - > > Key: SENTRY-320 > URL: https://issues.apache.org/jira/browse/SENTRY-320 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Ke Jia > Fix For: 1.8.0 > > Attachments: SENTRY-320-001.patch, SENTRY-320-002.patch, > SENTRY-320-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358401#comment-15358401 ] Dapeng Sun commented on SENTRY-1327: +1 > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch, SENTRY-1327-004.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1739/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1710/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1723/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1718/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1715/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1717/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1732/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1716/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1327) Enable "show grant role roleName on all" command
[ https://issues.apache.org/jira/browse/SENTRY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1327: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12811070/SENTRY-1327-002.patch against master. {color:red}Overall:{color} -1 due to 15 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.tools.TestSentryShellHive {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration {color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1714/console This message is automatically generated.) > Enable "show grant role roleName on all" command > > > Key: SENTRY-1327 > URL: https://issues.apache.org/jira/browse/SENTRY-1327 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1327-001.patch, SENTRY-1327-002.patch, > SENTRY-1327-003.patch > > > Now, Sentry already enable the "show grant role roleName on table(database)", > but not enable the "show grant role roleName on all" command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1375) Change Hive V2 as the default hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356598#comment-15356598 ] Dapeng Sun commented on SENTRY-1375: Thank Ke for the patch. [~sravya], do you have any comments about it? > Change Hive V2 as the default hive binding > -- > > Key: SENTRY-1375 > URL: https://issues.apache.org/jira/browse/SENTRY-1375 > Project: Sentry > Issue Type: Bug >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1375-001.patch, SENTRY-1375-002.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1358) Implement Grant role_name To User user_name in V2
[ https://issues.apache.org/jira/browse/SENTRY-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354780#comment-15354780 ] Dapeng Sun commented on SENTRY-1358: +1, please also add a link to refer the jira of V1 > Implement Grant role_name To User user_name in V2 > - > > Key: SENTRY-1358 > URL: https://issues.apache.org/jira/browse/SENTRY-1358 > Project: Sentry > Issue Type: Sub-task > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1358-001.patch > > > Implement Grant role_name To User user_name in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1094) SentryMetastorePostEventListener.onAlterTable should check for null dereference
[ https://issues.apache.org/jira/browse/SENTRY-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354754#comment-15354754 ] Dapeng Sun commented on SENTRY-1094: +1 > SentryMetastorePostEventListener.onAlterTable should check for null > dereference > --- > > Key: SENTRY-1094 > URL: https://issues.apache.org/jira/browse/SENTRY-1094 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Hao Hao >Assignee: Ke Jia > Attachments: SENTRY-1094-001.patch, SENTRY-1094-002.patch, > SENTRY-1094-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1354) add column level test cases for select ... group by, order by and where in V2
[ https://issues.apache.org/jira/browse/SENTRY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354755#comment-15354755 ] Dapeng Sun commented on SENTRY-1354: +1 > add column level test cases for select ... group by, order by and where in V2 > - > > Key: SENTRY-1354 > URL: https://issues.apache.org/jira/browse/SENTRY-1354 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1354-001.patch > > > add column level test cases for select ... group by, order by and where in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1354) add column level test cases for select ... group by, order by and where in V2
[ https://issues.apache.org/jira/browse/SENTRY-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354759#comment-15354759 ] Dapeng Sun commented on SENTRY-1354: Hi Ke, please add a link to refer the jira on V1 > add column level test cases for select ... group by, order by and where in V2 > - > > Key: SENTRY-1354 > URL: https://issues.apache.org/jira/browse/SENTRY-1354 > Project: Sentry > Issue Type: Bug > Components: Hive V2 >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1354-001.patch > > > add column level test cases for select ... group by, order by and where in V2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1375) Change Hive V2 as the default hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1375: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12814006/SENTRY-1375-001.patch against master. {color:red}Overall:{color} -1 due to 6 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.dbprovider.TestDbPrivilegesAtFunctionScope {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrUpdateOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrQueryOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrDocLevelOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrAdminOperations Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1798/console This message is automatically generated.) > Change Hive V2 as the default hive binding > -- > > Key: SENTRY-1375 > URL: https://issues.apache.org/jira/browse/SENTRY-1375 > Project: Sentry > Issue Type: Bug >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1375-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1375) Change Hive V2 as the default hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1375: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12814006/SENTRY-1375-001.patch against master. {color:red}Overall:{color} -1 due to 8 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.dbprovider.TestDbPrivilegesAtFunctionScope {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.ha.TestHaEnd2End {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.ha.TestHaEnd2End {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrAdminOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrUpdateOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrQueryOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrDocLevelOperations Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1801/console This message is automatically generated.) > Change Hive V2 as the default hive binding > -- > > Key: SENTRY-1375 > URL: https://issues.apache.org/jira/browse/SENTRY-1375 > Project: Sentry > Issue Type: Bug >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1375-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SENTRY-1375) Change Hive V2 as the default hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1375: --- Comment: was deleted (was: Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12814006/SENTRY-1375-001.patch against master. {color:red}Overall:{color} -1 due to 5 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrDocLevelOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrAdminOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrQueryOperations {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.solr.db.integration.TestSolrUpdateOperations Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1802/console This message is automatically generated.) > Change Hive V2 as the default hive binding > -- > > Key: SENTRY-1375 > URL: https://issues.apache.org/jira/browse/SENTRY-1375 > Project: Sentry > Issue Type: Bug >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1375-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1361) Refactor revokePrivilege of Sentry Client
[ https://issues.apache.org/jira/browse/SENTRY-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15354678#comment-15354678 ] Dapeng Sun commented on SENTRY-1361: SENTRY-1361: Refactor revokePrivilege of Sentry Client (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/6fbff11f Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/6fbff11f Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/6fbff11f > Refactor revokePrivilege of Sentry Client > -- > > Key: SENTRY-1361 > URL: https://issues.apache.org/jira/browse/SENTRY-1361 > Project: Sentry > Issue Type: Sub-task >Reporter: Dapeng Sun >Assignee: Ke Jia > Fix For: 1.8.0 > > Attachments: SENTRY-1361-001.patch, SENTRY-1361-001.patch, > SENTRY-1361-002.patch, SENTRY-1361-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1360) Refactor grantPrivilege of Sentry Client
[ https://issues.apache.org/jira/browse/SENTRY-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1360: --- Description: For SentryClient, TSentryPrivilege should be the parameter for grant/revoke privilege. it will be easy to extend Privilege. > Refactor grantPrivilege of Sentry Client > - > > Key: SENTRY-1360 > URL: https://issues.apache.org/jira/browse/SENTRY-1360 > Project: Sentry > Issue Type: Sub-task >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Fix For: 1.8.0 > > Attachments: SENTRY-1360.001.patch > > > For SentryClient, TSentryPrivilege should be the parameter for grant/revoke > privilege. it will be easy to extend Privilege. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1360) Refactor grantPrivilege of Sentry Client
[ https://issues.apache.org/jira/browse/SENTRY-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345990#comment-15345990 ] Dapeng Sun commented on SENTRY-1360: Patch uploaded > Refactor grantPrivilege of Sentry Client > - > > Key: SENTRY-1360 > URL: https://issues.apache.org/jira/browse/SENTRY-1360 > Project: Sentry > Issue Type: Sub-task >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Fix For: 1.8.0 > > Attachments: SENTRY-1360.001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1360) Refactor grantPrivilege of Sentry Client
[ https://issues.apache.org/jira/browse/SENTRY-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1360: --- Status: Patch Available (was: Open) > Refactor grantPrivilege of Sentry Client > - > > Key: SENTRY-1360 > URL: https://issues.apache.org/jira/browse/SENTRY-1360 > Project: Sentry > Issue Type: Sub-task >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Fix For: 1.8.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SENTRY-1361) Refactor revokePrivilege of Sentry Client
Dapeng Sun created SENTRY-1361: -- Summary: Refactor revokePrivilege of Sentry Client Key: SENTRY-1361 URL: https://issues.apache.org/jira/browse/SENTRY-1361 Project: Sentry Issue Type: Sub-task Reporter: Dapeng Sun Assignee: Ke Jia -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SENTRY-1360) Refactor grantPrivilege of Sentry Client
Dapeng Sun created SENTRY-1360: -- Summary: Refactor grantPrivilege of Sentry Client Key: SENTRY-1360 URL: https://issues.apache.org/jira/browse/SENTRY-1360 Project: Sentry Issue Type: Sub-task Reporter: Dapeng Sun Assignee: Dapeng Sun -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1068) Allow user who created a table to have "with grant" over that table by default
[ https://issues.apache.org/jira/browse/SENTRY-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1068: --- Attachment: SENTRY-1068.002.patch > Allow user who created a table to have "with grant" over that table by default > -- > > Key: SENTRY-1068 > URL: https://issues.apache.org/jira/browse/SENTRY-1068 > Project: Sentry > Issue Type: Improvement >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Labels: hive, roadmap > Fix For: 1.8.0 > > Attachments: SENTRY-1068.001.patch, SENTRY-1068.002.patch > > > The database(table) owner should have "with grant" over that table, so that > the owner can grant the privilege to others -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1068) Allow user who created a table to have "with grant" over that table by default
[ https://issues.apache.org/jira/browse/SENTRY-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1068: --- Status: Patch Available (was: In Progress) > Allow user who created a table to have "with grant" over that table by default > -- > > Key: SENTRY-1068 > URL: https://issues.apache.org/jira/browse/SENTRY-1068 > Project: Sentry > Issue Type: Improvement >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Labels: hive, roadmap > Fix For: 1.8.0 > > Attachments: SENTRY-1068.001.patch > > > The database(table) owner should have "with grant" over that table, so that > the owner can grant the privilege to others -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1348) Move HA related class from sentry-provider-db to sentry-service-common
[ https://issues.apache.org/jira/browse/SENTRY-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343160#comment-15343160 ] Dapeng Sun commented on SENTRY-1348: +1 > Move HA related class from sentry-provider-db to sentry-service-common > -- > > Key: SENTRY-1348 > URL: https://issues.apache.org/jira/browse/SENTRY-1348 > Project: Sentry > Issue Type: Sub-task >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 1.8.0 > > Attachments: SENTRY-1348.001-SENTRY-1205.patch, > SENTRY-1348.002-SENTRY-1205.patch > > > Move HA related class from sentry-provider-db to sentry-service-common -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SENTRY-1146) Sentry TLP: Update sentry website after graduation
[ https://issues.apache.org/jira/browse/SENTRY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun resolved SENTRY-1146. Resolution: Fixed > Sentry TLP: Update sentry website after graduation > -- > > Key: SENTRY-1146 > URL: https://issues.apache.org/jira/browse/SENTRY-1146 > Project: Sentry > Issue Type: Bug >Reporter: Dapeng Sun >Assignee: Dapeng Sun > > After Sentry is graduated from incubator, a series of pages in Sentry web > need to update. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1302) Update Hive V2 after moving Exception to sentry-core-common module
[ https://issues.apache.org/jira/browse/SENTRY-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1302: --- Resolution: Fixed Status: Resolved (was: Patch Available) SENTRY-1302: Update Hive V2 after moving Exception to sentry-core-common module (Ke Jia via Dapeng Sun) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/8b8442bb Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/8b8442bb Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/8b8442bb > Update Hive V2 after moving Exception to sentry-core-common module > -- > > Key: SENTRY-1302 > URL: https://issues.apache.org/jira/browse/SENTRY-1302 > Project: Sentry > Issue Type: Bug >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1302-001.patch > > > Update Hive V2 after moving Exception to sentry-core-common > module(https://issues.apache.org/jira/browse/SENTRY-1289) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1134) Add user defined udf test case
[ https://issues.apache.org/jira/browse/SENTRY-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1134: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thank Ke, committed SENTRY-1134: Add user defined udf test case (Ke Jia, reviewed Dapeng Sun, Anne Yu) Project: http://git-wip-us.apache.org/repos/asf/sentry/repo Commit: http://git-wip-us.apache.org/repos/asf/sentry/commit/8cd392b5 Tree: http://git-wip-us.apache.org/repos/asf/sentry/tree/8cd392b5 Diff: http://git-wip-us.apache.org/repos/asf/sentry/diff/8cd392b5 > Add user defined udf test case > -- > > Key: SENTRY-1134 > URL: https://issues.apache.org/jira/browse/SENTRY-1134 > Project: Sentry > Issue Type: New Feature > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Anne Yu >Assignee: Ke Jia > Attachments: SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, > SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, SENTRY-1134-002.patch, > SENTRY-1134-004.patch, SENTRY-1134.003.patch > > > Add user defined UDF test, user create a jar then create udf from this jar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1344) Move AuthorizationComponent from sentry-provider-common to sentry-core-common
[ https://issues.apache.org/jira/browse/SENTRY-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340848#comment-15340848 ] Dapeng Sun commented on SENTRY-1344: +1 > Move AuthorizationComponent from sentry-provider-common to sentry-core-common > - > > Key: SENTRY-1344 > URL: https://issues.apache.org/jira/browse/SENTRY-1344 > Project: Sentry > Issue Type: Sub-task >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 1.8.0 > > Attachments: SENTRY-1344.001-SENTRY-1205.patch > > > Move AuthorizationComponent from sentry-provider-common to sentry-core-common -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-320) show role grant group groupname should not throw an exception if group doesnt exist in db
[ https://issues.apache.org/jira/browse/SENTRY-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333093#comment-15333093 ] Dapeng Sun commented on SENTRY-320: --- +1 > show role grant group groupname should not throw an exception if group doesnt > exist in db > - > > Key: SENTRY-320 > URL: https://issues.apache.org/jira/browse/SENTRY-320 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Ke Jia > Fix For: 1.8.0 > > Attachments: SENTRY-320-001.patch, SENTRY-320-002.patch, > SENTRY-320-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1332) .
[ https://issues.apache.org/jira/browse/SENTRY-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1332: --- Summary: . (was: Remove log dependence.) > . > - > > Key: SENTRY-1332 > URL: https://issues.apache.org/jira/browse/SENTRY-1332 > Project: Sentry > Issue Type: Bug >Reporter: Dapeng Sun >Assignee: Dapeng Sun > > According the discussion in commons-dev, we will remove the log dependence of > common-logging. > About the logging of native library failure, users of CRYPTO could get the > information about whether native is enabled or native failure reason from > org.apache.commons.crypto.utils.NativeCodeLoader#isNativeCodeLoaded() or > org.apache.commons.crypto.cipher.Openssl#loadingFailureReason(), they could > log these information in their system if they need. > At the same time, I think we can add an option for "native only" (Currently, > when loading native failed, we log native failure error and use JCE > implementation as fallback directly), the property in configuration may like > "ENABLE_FALLBACK_ON_NATIVE_FAILED", if user disable the option, it could > throw an exception when loading native failed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1332) .
[ https://issues.apache.org/jira/browse/SENTRY-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1332: --- Description: . (was: According the discussion in commons-dev, we will remove the log dependence of common-logging. About the logging of native library failure, users of CRYPTO could get the information about whether native is enabled or native failure reason from org.apache.commons.crypto.utils.NativeCodeLoader#isNativeCodeLoaded() or org.apache.commons.crypto.cipher.Openssl#loadingFailureReason(), they could log these information in their system if they need. At the same time, I think we can add an option for "native only" (Currently, when loading native failed, we log native failure error and use JCE implementation as fallback directly), the property in configuration may like "ENABLE_FALLBACK_ON_NATIVE_FAILED", if user disable the option, it could throw an exception when loading native failed. ) > . > - > > Key: SENTRY-1332 > URL: https://issues.apache.org/jira/browse/SENTRY-1332 > Project: Sentry > Issue Type: Bug >Reporter: Dapeng Sun >Assignee: Dapeng Sun > > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-950) add column level test cases for select ... group by, order by and where
[ https://issues.apache.org/jira/browse/SENTRY-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-950: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to master, thank you for the contribution. > add column level test cases for select ... group by, order by and where > --- > > Key: SENTRY-950 > URL: https://issues.apache.org/jira/browse/SENTRY-950 > Project: Sentry > Issue Type: Task >Reporter: Anne Yu >Assignee: Ke Jia > Attachments: SENTRY-950-001.patch, SENTRY-950-001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1304) Enable CREATEMACRO and DROPMACRO operations in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316136#comment-15316136 ] Dapeng Sun commented on SENTRY-1304: Committed to master, thank Ke. > Enable CREATEMACRO and DROPMACRO operations in hive binding > > > Key: SENTRY-1304 > URL: https://issues.apache.org/jira/browse/SENTRY-1304 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1304-001.patch > > > Enable CREATEMACRO and DROPMACRO operations in hive binding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1134) Add user defined udf test case
[ https://issues.apache.org/jira/browse/SENTRY-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313888#comment-15313888 ] Dapeng Sun commented on SENTRY-1134: Thank Ke, it's better to choose a new function name. > Add user defined udf test case > -- > > Key: SENTRY-1134 > URL: https://issues.apache.org/jira/browse/SENTRY-1134 > Project: Sentry > Issue Type: New Feature > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Anne Yu >Assignee: Anne Yu > Attachments: SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, > SENTRY-1134-001 .patch, SENTRY-1134-001 .patch, SENTRY-1134-002.patch, > SENTRY-1134.003.patch > > > Add user defined UDF test, user create a jar then create udf from this jar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-872) Uber jira for HMS HA + Sentry HA with HDFS plugin improvements
[ https://issues.apache.org/jira/browse/SENTRY-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309300#comment-15309300 ] Dapeng Sun edited comment on SENTRY-872 at 6/1/16 5:29 AM: --- Thank [~cmccabe] for the design. Here are my comments: To avoiding Hive MetaStore send many duplicate information to Sentry Server, if Hive side can provide the Hive replication support, it would be good. I think another solution would be selecting a leader from HiveMetaListeners when Hive Metastores starting, in sync mode, other listeners must wait the leader finish sync the metadata to Sentry. After the leader Metastore started, other Metastore could be back to work. About Sentry HA, currently sentry server service is stateless, it's better to keep it stateless and not cover it to active/passive mode, since we have plan to persist {{Sentry Update Log}} to database. I think sentry servers could share states by Zookeeper and database. was (Author: dapengsun): Thank [~cmccabe] for the design. Here are my comments: In Hive side, to avoiding Hive MetaStore send many duplicate information to Sentry Server, if Hive side can provide the Hive replication support, it would be good. I think another solution would be selecting a leader from HiveMetaListeners when Hive Metastores starting, in sync mode, other listeners must wait the leader finish sync the metadata to Sentry. After the leader Metastore started, other Metastore could be back to work. About Sentry HA, currently sentry server service is stateless, it's better to keep it stateless and not cover it to active/passive mode, since we have plan to persist {{Sentry Update Log}} to database. I think sentry servers could share states by Zookeeper and database. > Uber jira for HMS HA + Sentry HA with HDFS plugin improvements > -- > > Key: SENTRY-872 > URL: https://issues.apache.org/jira/browse/SENTRY-872 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 1.8.0 > > Attachments: SENTRY-872.0.patch, SENTRY-872.pdf, SENTRY-872_design.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-872) Uber jira for HMS HA + Sentry HA with HDFS plugin improvements
[ https://issues.apache.org/jira/browse/SENTRY-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309300#comment-15309300 ] Dapeng Sun edited comment on SENTRY-872 at 6/1/16 5:30 AM: --- Thank [~cmccabe] for the design. Here are my comments: To avoiding Hive MetaStore send many duplicate information to Sentry Server, if Hive side can provide the Hive replication support, it would be good. I think another solution would be selecting a leader from HiveMetaListeners when Hive Metastores starting, in sync mode, other listeners must wait the leader finish sync the metadata to Sentry. After the leader Metastore started, other Metastore could be back to work. About Sentry HA, currently sentry server service is stateless, it's better to keep it stateless and not cover it to active/passive mode, since we have plan to persist {{Sentry Update Log}} to database. I think sentry servers could share states by Zookeeper and database. was (Author: dapengsun): Thank [~cmccabe] for the design. Here are my comments: To avoiding Hive MetaStore send many duplicate information to Sentry Server, if Hive side can provide the Hive replication support, it would be good. I think another solution would be selecting a leader from HiveMetaListeners when Hive Metastores starting, in sync mode, other listeners must wait the leader finish sync the metadata to Sentry. After the leader Metastore started, other Metastore could be back to work. About Sentry HA, currently sentry server service is stateless, it's better to keep it stateless and not cover it to active/passive mode, since we have plan to persist {{Sentry Update Log}} to database. I think sentry servers could share states by Zookeeper and database. > Uber jira for HMS HA + Sentry HA with HDFS plugin improvements > -- > > Key: SENTRY-872 > URL: https://issues.apache.org/jira/browse/SENTRY-872 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 1.8.0 > > Attachments: SENTRY-872.0.patch, SENTRY-872.pdf, SENTRY-872_design.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1272) Enable ALTERVIEW_RENAME and ALTERVIEW_AS operation in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1272: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thank [~Jk_Self] > Enable ALTERVIEW_RENAME and ALTERVIEW_AS operation in hive binding > --- > > Key: SENTRY-1272 > URL: https://issues.apache.org/jira/browse/SENTRY-1272 > Project: Sentry > Issue Type: Sub-task > Components: Hive Binding >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1272.001.patch, SENTRY-1272.002.patch, > SENTRY-1272.002.patch > > > Enable ALTERVIEW_RENAME and ALTERVIEW_AS operation in hive binding -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1283) Enable alter table operation without outputs in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1283: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. Thank [~Jk_Self] > Enable alter table operation without outputs in hive binding > > > Key: SENTRY-1283 > URL: https://issues.apache.org/jira/browse/SENTRY-1283 > Project: Sentry > Issue Type: Sub-task > Components: Hive Binding >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1283.001.patch, SENTRY-1283.002.patch > > > Enable ALTERTABLE_PARTCOLTYPE,ALTERPARTITION_BUCKETNUM,ALTERTABLE_BUCKETNUM > in hive binding. All these operations don't have outputs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1304) Enable CREATEMACRO and DROPMACRO operations in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309079#comment-15309079 ] Dapeng Sun commented on SENTRY-1304: +1 > Enable CREATEMACRO and DROPMACRO operations in hive binding > > > Key: SENTRY-1304 > URL: https://issues.apache.org/jira/browse/SENTRY-1304 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1304-001.patch > > > Enable CREATEMACRO and DROPMACRO operations in hive binding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1086) Add permission check and test case for alter db set owner
[ https://issues.apache.org/jira/browse/SENTRY-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1086: --- Issue Type: Sub-task (was: Test) Parent: SENTRY-1271 > Add permission check and test case for alter db set owner > - > > Key: SENTRY-1086 > URL: https://issues.apache.org/jira/browse/SENTRY-1086 > Project: Sentry > Issue Type: Sub-task >Reporter: Sravya Tirukkovalur >Assignee: Ke Jia >Priority: Minor > Attachments: SENTRY-1086.001.patch, SENTRY-1086.001.patch > > > alter database db1 set owner user abc; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SENTRY-522) [Unit Test] TestExportImportPrivileges failed due to error "Couldn't access new HiveServer: "
[ https://issues.apache.org/jira/browse/SENTRY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun resolved SENTRY-522. --- Resolution: Cannot Reproduce Test passed in my local environment, closed as "cannot reproduce" > [Unit Test] TestExportImportPrivileges failed due to error "Couldn't access > new HiveServer: " > - > > Key: SENTRY-522 > URL: https://issues.apache.org/jira/browse/SENTRY-522 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Lenni Kuff >Priority: Blocker > Fix For: 1.8.0 > > > Failure: > https://builds.apache.org/view/S-Z/view/Sentry/job/Sentry-jdk-1.7/97/org.apache.sentry$sentry-tests-hive/testReport/junit/org.apache.sentry.tests.e2e.hive/TestExportImportPrivileges/org_apache_sentry_tests_e2e_hive_TestExportImportPrivileges/ > {code} > Error Message > Couldn't access new HiveServer: jdbc:hive2://localhost:34410/default > Stacktrace > java.util.concurrent.TimeoutException: Couldn't access new HiveServer: > jdbc:hive2://localhost:34410/default > at > org.apache.sentry.tests.e2e.hive.hiveserver.AbstractHiveServer.waitForStartup(AbstractHiveServer.java:80) > at > org.apache.sentry.tests.e2e.hive.hiveserver.InternalHiveServer.start(InternalHiveServer.java:47) > at > org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.setupTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:229) > 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:44) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:292) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Seems like there may have been an issue with HDFS: > {code} > java.lang.IllegalStateException: Unable to finalize edits file > /tmp/1415867520531-0/dfs/name2/current/edits_inprogress_001 > at > org.apache.hadoop.hdfs.server.namenode.FileJournalManager.finalizeLogSegment(FileJournalManager.java:141) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet$4.apply(JournalSet.java:236) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet.mapJournalsAndReportErrors(JournalSet.java:393) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet.finalizeLogSegment(JournalSet.java:231) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.endCurrentLogSegment(FSEditLog.java:1216) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.close(FSEditLog.java:356) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.stopActiveServices(FSNamesystem.java:1224) > at > org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.stopActiveServices(NameNode.java:1638) > at > org.apache.hadoop.hdfs.server.namenode.ha.ActiveState.exitState(ActiveState.java:70) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.stop(NameNode.java:803) > at > org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:1592) > at > org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:1571) > at org.apache.sentry.tests.e2e.hive.fs.MiniDFS.tearDown(MiniDFS.java:76) > at > org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.tearDownTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:478) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at >
[jira] [Comment Edited] (SENTRY-522) [Unit Test] TestExportImportPrivileges failed due to error "Couldn't access new HiveServer: "
[ https://issues.apache.org/jira/browse/SENTRY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299310#comment-15299310 ] Dapeng Sun edited comment on SENTRY-522 at 5/25/16 1:44 AM: Test passed in my local environment, closed as "cannot reproduce". Please reopen it if it still exist. was (Author: dapengsun): Test passed in my local environment, closed as "cannot reproduce" > [Unit Test] TestExportImportPrivileges failed due to error "Couldn't access > new HiveServer: " > - > > Key: SENTRY-522 > URL: https://issues.apache.org/jira/browse/SENTRY-522 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Lenni Kuff >Priority: Blocker > Fix For: 1.8.0 > > > Failure: > https://builds.apache.org/view/S-Z/view/Sentry/job/Sentry-jdk-1.7/97/org.apache.sentry$sentry-tests-hive/testReport/junit/org.apache.sentry.tests.e2e.hive/TestExportImportPrivileges/org_apache_sentry_tests_e2e_hive_TestExportImportPrivileges/ > {code} > Error Message > Couldn't access new HiveServer: jdbc:hive2://localhost:34410/default > Stacktrace > java.util.concurrent.TimeoutException: Couldn't access new HiveServer: > jdbc:hive2://localhost:34410/default > at > org.apache.sentry.tests.e2e.hive.hiveserver.AbstractHiveServer.waitForStartup(AbstractHiveServer.java:80) > at > org.apache.sentry.tests.e2e.hive.hiveserver.InternalHiveServer.start(InternalHiveServer.java:47) > at > org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.setupTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:229) > 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:44) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:292) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} > Seems like there may have been an issue with HDFS: > {code} > java.lang.IllegalStateException: Unable to finalize edits file > /tmp/1415867520531-0/dfs/name2/current/edits_inprogress_001 > at > org.apache.hadoop.hdfs.server.namenode.FileJournalManager.finalizeLogSegment(FileJournalManager.java:141) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet$4.apply(JournalSet.java:236) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet.mapJournalsAndReportErrors(JournalSet.java:393) > at > org.apache.hadoop.hdfs.server.namenode.JournalSet.finalizeLogSegment(JournalSet.java:231) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.endCurrentLogSegment(FSEditLog.java:1216) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.close(FSEditLog.java:356) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.stopActiveServices(FSNamesystem.java:1224) > at > org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.stopActiveServices(NameNode.java:1638) > at > org.apache.hadoop.hdfs.server.namenode.ha.ActiveState.exitState(ActiveState.java:70) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.stop(NameNode.java:803) > at > org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:1592) > at > org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:1571) > at org.apache.sentry.tests.e2e.hive.fs.MiniDFS.tearDown(MiniDFS.java:76) > at > org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.tearDownTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:478) > at
[jira] [Updated] (SENTRY-1274) Enable ALTERVIEW_AS in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-1274: --- Issue Type: Improvement (was: Sub-task) Parent: (was: SENTRY-1271) > Enable ALTERVIEW_AS in hive binding > --- > > Key: SENTRY-1274 > URL: https://issues.apache.org/jira/browse/SENTRY-1274 > Project: Sentry > Issue Type: Improvement >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1274.001.patch, SENTRY-1274.001.patch > > > Enable ALTERVIEW_AS in hive binding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-1274) Enable ALTERVIEW_AS in hive binding
[ https://issues.apache.org/jira/browse/SENTRY-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297687#comment-15297687 ] Dapeng Sun edited comment on SENTRY-1274 at 5/24/16 5:06 AM: - Thank [~Jk_Self], I closed this jira as duplicated was (Author: dapengsun): Thank [~Jk_Self], I close this jira as duplicated > Enable ALTERVIEW_AS in hive binding > --- > > Key: SENTRY-1274 > URL: https://issues.apache.org/jira/browse/SENTRY-1274 > Project: Sentry > Issue Type: Sub-task >Reporter: Ke Jia >Assignee: Ke Jia > Attachments: SENTRY-1274.001.patch, SENTRY-1274.001.patch > > > Enable ALTERVIEW_AS in hive binding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)