[jira] [Created] (SENTRY-2019) Improve logging on SentryPlugin
Vadim Spector created SENTRY-2019: - Summary: Improve logging on SentryPlugin Key: SENTRY-2019 URL: https://issues.apache.org/jira/browse/SENTRY-2019 Project: Sentry Issue Type: Improvement Reporter: Vadim Spector Assignee: Vadim Spector For supportability, need detailed logging of data flow in and from SentryPlugin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1475) Integrate Sentry with Solr authorization framework
[
https://issues.apache.org/jira/browse/SENTRY-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215913#comment-16215913
]
Hadoop QA commented on SENTRY-1475:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12893595/SENTRY-1475.1.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.tools.TestSentryConfigToolSolr
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3371/console
This message is automatically generated.
> Integrate Sentry with Solr authorization framework
> --
>
> Key: SENTRY-1475
> URL: https://issues.apache.org/jira/browse/SENTRY-1475
> Project: Sentry
> Issue Type: New Feature
> Components: Sentry, Solr Plugin
>Reporter: Hrishikesh Gadre
> Fix For: 2.0.0
>
> Attachments: SENTRY-1475.1.patch
>
>
> Solr 6 has added support for pluggable authorization modules. We should
> integrate Sentry within this authorization framework.
> https://cwiki.apache.org/confluence/display/solr/Authentication+and+Authorization+Plugins
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-2017) Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog
[ https://issues.apache.org/jira/browse/SENTRY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2017: Status: Patch Available (was: Open) > Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog > --- > > Key: SENTRY-2017 > URL: https://issues.apache.org/jira/browse/SENTRY-2017 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Attachments: SENTRY-2017.001.patch > > > Currently sentry hive e2e tests are using SentryMetastorePostEventListener > instead of SentryMetastorePostEventListenerNotificationLog. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1475) Integrate Sentry with Solr authorization framework
[ https://issues.apache.org/jira/browse/SENTRY-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215852#comment-16215852 ] Sergio Peña commented on SENTRY-1475: - [~hgadre] Could you submit the patch to Review Board as well? and post the link here. > Integrate Sentry with Solr authorization framework > -- > > Key: SENTRY-1475 > URL: https://issues.apache.org/jira/browse/SENTRY-1475 > Project: Sentry > Issue Type: New Feature > Components: Sentry, Solr Plugin >Reporter: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1475.1.patch > > > Solr 6 has added support for pluggable authorization modules. We should > integrate Sentry within this authorization framework. > https://cwiki.apache.org/confluence/display/solr/Authentication+and+Authorization+Plugins -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1475) Integrate Sentry with Solr authorization framework
[ https://issues.apache.org/jira/browse/SENTRY-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergio Peña updated SENTRY-1475: Status: Patch Available (was: Open) > Integrate Sentry with Solr authorization framework > -- > > Key: SENTRY-1475 > URL: https://issues.apache.org/jira/browse/SENTRY-1475 > Project: Sentry > Issue Type: New Feature > Components: Sentry, Solr Plugin >Reporter: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1475.1.patch > > > Solr 6 has added support for pluggable authorization modules. We should > integrate Sentry within this authorization framework. > https://cwiki.apache.org/confluence/display/solr/Authentication+and+Authorization+Plugins -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1475) Integrate Sentry with Solr authorization framework
[ https://issues.apache.org/jira/browse/SENTRY-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrishikesh Gadre updated SENTRY-1475: - Attachment: SENTRY-1475.1.patch [~spena] could you please take a look? > Integrate Sentry with Solr authorization framework > -- > > Key: SENTRY-1475 > URL: https://issues.apache.org/jira/browse/SENTRY-1475 > Project: Sentry > Issue Type: New Feature > Components: Sentry, Solr Plugin >Reporter: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1475.1.patch > > > Solr 6 has added support for pluggable authorization modules. We should > integrate Sentry within this authorization framework. > https://cwiki.apache.org/confluence/display/solr/Authentication+and+Authorization+Plugins -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENTRY-2018) Remove SentryMetastorePostEventListener and SentryMetastorePostEventListenerBase classes
kalyan kumar kalvagadda created SENTRY-2018: --- Summary: Remove SentryMetastorePostEventListener and SentryMetastorePostEventListenerBase classes Key: SENTRY-2018 URL: https://issues.apache.org/jira/browse/SENTRY-2018 Project: Sentry Issue Type: Bug Components: Sentry Affects Versions: 2.0.0 Reporter: kalyan kumar kalvagadda Assignee: kalyan kumar kalvagadda SentryMetastorePostEventListener and SentryMetastorePostEventListenerBase classes are obsolete now and can be removed, -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2017) Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog
[ https://issues.apache.org/jira/browse/SENTRY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2017: Attachment: SENTRY-2017.001.patch > Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog > --- > > Key: SENTRY-2017 > URL: https://issues.apache.org/jira/browse/SENTRY-2017 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Attachments: SENTRY-2017.001.patch > > > Currently sentry hive e2e tests are using SentryMetastorePostEventListener > instead of SentryMetastorePostEventListenerNotificationLog. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENTRY-2017) Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog
kalyan kumar kalvagadda created SENTRY-2017: --- Summary: Fix Sentry e2e tests to use SentryMetastorePostEventListenerNotificationLog Key: SENTRY-2017 URL: https://issues.apache.org/jira/browse/SENTRY-2017 Project: Sentry Issue Type: Bug Components: Sentry Affects Versions: 2.0.0 Reporter: kalyan kumar kalvagadda Assignee: kalyan kumar kalvagadda Currently sentry hive e2e tests are using SentryMetastorePostEventListener instead of SentryMetastorePostEventListenerNotificationLog. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENTRY-2016) Change default web port to something closer inline to other Sentry ports
Brian Towles created SENTRY-2016: Summary: Change default web port to something closer inline to other Sentry ports Key: SENTRY-2016 URL: https://issues.apache.org/jira/browse/SENTRY-2016 Project: Sentry Issue Type: Improvement Reporter: Brian Towles Priority: Trivial The current web port is 29000 and was set by SENTRY-914. The problem is that the ports are fairly separated and does not allow for a simple port range passthrough for firewalls or network access control lists. If we change the default web-port to be 8039 it would be contiguous with the thrift port it will allow for easier network implementations and consistent grouping. Something like: Default Thrift Port: 8038 Default Web Port: 8039 This is still in unassigned IANA range of 8035-8039 tcp,udp (https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=unassigned=4). And any furture ports could go down to 8035 As well this would still be overridable in the normal way incase of collisions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-2015) Refactor Command implementations
[
https://issues.apache.org/jira/browse/SENTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215257#comment-16215257
]
Hadoop QA commented on SENTRY-2015:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12893521/SENTRY-2015.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3370/console
This message is automatically generated.
> Refactor Command implementations
>
>
> Key: SENTRY-2015
> URL: https://issues.apache.org/jira/browse/SENTRY-2015
> Project: Sentry
> Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 2.0.0
>
> Attachments: SENTRY-2015.patch
>
>
> Right now, we have different Command implementations for each possible Shell
> command for both the Hive and Generic versions. Instead, we should have a
> single interface which encapsulates all of the different Commands, and then
> two implementations for Hive + Generic. Apart from having a lot less simple
> classes, this means that I can re-use this interface for the Sentry CLI work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-2015) Refactor Command implementations
[ https://issues.apache.org/jira/browse/SENTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-2015: Status: Patch Available (was: Open) > Refactor Command implementations > > > Key: SENTRY-2015 > URL: https://issues.apache.org/jira/browse/SENTRY-2015 > Project: Sentry > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 2.0.0 > > Attachments: SENTRY-2015.patch > > > Right now, we have different Command implementations for each possible Shell > command for both the Hive and Generic versions. Instead, we should have a > single interface which encapsulates all of the different Commands, and then > two implementations for Hive + Generic. Apart from having a lot less simple > classes, this means that I can re-use this interface for the Sentry CLI work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2015) Refactor Command implementations
[ https://issues.apache.org/jira/browse/SENTRY-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-2015: Attachment: SENTRY-2015.patch > Refactor Command implementations > > > Key: SENTRY-2015 > URL: https://issues.apache.org/jira/browse/SENTRY-2015 > Project: Sentry > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 2.0.0 > > Attachments: SENTRY-2015.patch > > > Right now, we have different Command implementations for each possible Shell > command for both the Hive and Generic versions. Instead, we should have a > single interface which encapsulates all of the different Commands, and then > two implementations for Hive + Generic. Apart from having a lot less simple > classes, this means that I can re-use this interface for the Sentry CLI work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENTRY-2015) Refactor Command implementations
Colm O hEigeartaigh created SENTRY-2015: --- Summary: Refactor Command implementations Key: SENTRY-2015 URL: https://issues.apache.org/jira/browse/SENTRY-2015 Project: Sentry Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0 Right now, we have different Command implementations for each possible Shell command for both the Hive and Generic versions. Instead, we should have a single interface which encapsulates all of the different Commands, and then two implementations for Hive + Generic. Apart from having a lot less simple classes, this means that I can re-use this interface for the Sentry CLI work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
