[jira] [Updated] (SENTRY-1863) Update Sentry website to reflect 1.8.0 release
[ https://issues.apache.org/jira/browse/SENTRY-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1863: Fix Version/s: 2.0.0 > Update Sentry website to reflect 1.8.0 release > -- > > Key: SENTRY-1863 > URL: https://issues.apache.org/jira/browse/SENTRY-1863 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Sergio Peña >Assignee: Sergio Peña > Fix For: 2.0.0 > > Attachments: SENTRY-1863.1.patch > > > These pages will need to be updated: > - http://sentry.apache.org/general/downloads.html > - http://sentry.apache.org/general/history.html > The SVN repo where to update this is the following link: > https://svn.apache.org/repos/asf/sentry/site/trunk/content/general -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1851) Revert HMSFollower refactoring change
[ https://issues.apache.org/jira/browse/SENTRY-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1851: Fix Version/s: 2.0.0 > Revert HMSFollower refactoring change > - > > Key: SENTRY-1851 > URL: https://issues.apache.org/jira/browse/SENTRY-1851 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Fix For: 2.0.0 > > Attachments: SENTRY-1851.001-sentry-ha-redesign.patch > > > Code change that were committed as part of SENTRY-1769 has issues cherry > picking as there are couple of files are refactored a lot and also have been > renamed. > As the files were renamed in an attempt to follow google code style. This is > something that is not needed if it is creating issues. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2061) Prepare release notes for 2.0.0 release
[ https://issues.apache.org/jira/browse/SENTRY-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2061: Labels: release (was: ) > Prepare release notes for 2.0.0 release > --- > > Key: SENTRY-2061 > URL: https://issues.apache.org/jira/browse/SENTRY-2061 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: release > Fix For: 2.0.0 > > > This jira is created to track the the notes that are to be documented for > release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2059) Fix the tests to use transaction listeners for handling HMS Notifications.
[ https://issues.apache.org/jira/browse/SENTRY-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2059: Attachment: SENTRY-2059.002.patch > Fix the tests to use transaction listeners for handling HMS Notifications. > -- > > Key: SENTRY-2059 > URL: https://issues.apache.org/jira/browse/SENTRY-2059 > Project: Sentry > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Attachments: SENTRY-2059.002.patch, SENTRY-2059.002.patch > > > Currently DbNotificationListener and > SentryMetastorePostEventListenerNotificationLog are using not configured as > transactional listeners. They should be configured as transactional listeners. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1863) Update Sentry website to reflect 1.8.0 release
[ https://issues.apache.org/jira/browse/SENTRY-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1863: Fix Version/s: (was: 2.0.0) 1.8.0 > Update Sentry website to reflect 1.8.0 release > -- > > Key: SENTRY-1863 > URL: https://issues.apache.org/jira/browse/SENTRY-1863 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Sergio Peña >Assignee: Sergio Peña > Fix For: 1.8.0 > > Attachments: SENTRY-1863.1.patch > > > These pages will need to be updated: > - http://sentry.apache.org/general/downloads.html > - http://sentry.apache.org/general/history.html > The SVN repo where to update this is the following link: > https://svn.apache.org/repos/asf/sentry/site/trunk/content/general -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1862) Create 1.8.0 artifacts. sign and upload to sentry package repo
[ https://issues.apache.org/jira/browse/SENTRY-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1862: Fix Version/s: (was: 2.0.0) 1.8.0 > Create 1.8.0 artifacts. sign and upload to sentry package repo > -- > > Key: SENTRY-1862 > URL: https://issues.apache.org/jira/browse/SENTRY-1862 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Sergio Peña >Assignee: Colm O hEigeartaigh > Fix For: 1.8.0 > > > Once release-1.8.0 is ready and no fixes are needed, then we should create > jars, sign them and upload them to the repo. > I'll add more details later. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2042) Support file based Sentry provider for Solr plugin
[ https://issues.apache.org/jira/browse/SENTRY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2042: Resolution: Fixed Status: Resolved (was: Patch Available) > Support file based Sentry provider for Solr plugin > -- > > Key: SENTRY-2042 > URL: https://issues.apache.org/jira/browse/SENTRY-2042 > Project: Sentry > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-2042.001.patch, SENTRY-2042.1.patch, > SENTRY-2042.2.patch, SENTRY-2042.2.patch > > > As part of SENTRY-1475, we upgraded the Sentry/Solr integration to use the > latest version of SOLR (7.1.0 at the time of writing). But this did not > include the support for file-based Sentry provider backend. This jira is to > track the work required to integrate file based Sentry provider backend with > Solr plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-2042) Support file based Sentry provider for Solr plugin
[ https://issues.apache.org/jira/browse/SENTRY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259943#comment-16259943 ] kalyan kumar kalvagadda commented on SENTRY-2042: - [~hgadre] Thanks for the contribution. > Support file based Sentry provider for Solr plugin > -- > > Key: SENTRY-2042 > URL: https://issues.apache.org/jira/browse/SENTRY-2042 > Project: Sentry > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-2042.001.patch, SENTRY-2042.1.patch, > SENTRY-2042.2.patch, SENTRY-2042.2.patch > > > As part of SENTRY-1475, we upgraded the Sentry/Solr integration to use the > latest version of SOLR (7.1.0 at the time of writing). But this did not > include the support for file-based Sentry provider backend. This jira is to > track the work required to integrate file based Sentry provider backend with > Solr plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2059) Fix the tests to use transaction listeners for handling HMS Notifications.
[ https://issues.apache.org/jira/browse/SENTRY-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2059: Attachment: (was: SENTRY-2059.002.patch) > Fix the tests to use transaction listeners for handling HMS Notifications. > -- > > Key: SENTRY-2059 > URL: https://issues.apache.org/jira/browse/SENTRY-2059 > Project: Sentry > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Attachments: SENTRY-2059.002.patch > > > Currently DbNotificationListener and > SentryMetastorePostEventListenerNotificationLog are using not configured as > transactional listeners. They should be configured as transactional listeners. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2059) Fix the tests to use transaction listeners for handling HMS Notifications.
[ https://issues.apache.org/jira/browse/SENTRY-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2059: Attachment: SENTRY-2059.002.patch > Fix the tests to use transaction listeners for handling HMS Notifications. > -- > > Key: SENTRY-2059 > URL: https://issues.apache.org/jira/browse/SENTRY-2059 > Project: Sentry > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Attachments: SENTRY-2059.002.patch, SENTRY-2059.002.patch > > > Currently DbNotificationListener and > SentryMetastorePostEventListenerNotificationLog are using not configured as > transactional listeners. They should be configured as transactional listeners. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1480) A upgrade tool to migrate Solr/Sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261561#comment-16261561 ] kalyan kumar kalvagadda commented on SENTRY-1480: - [~hgadre] Please update the latest patch > A upgrade tool to migrate Solr/Sentry permissions > -- > > Key: SENTRY-1480 > URL: https://issues.apache.org/jira/browse/SENTRY-1480 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1480.1.patch > > > SENTRY-1475 is tracking the integration between Solr 7 and Sentry. Currently > admin privileges for Solr are defined using "admin" as the collection name > (i.e. Sentry reuses collection level permissions for admin operations). > Solr 7, on the other hand, provides a pluggable authorization framework with > fine-grained permissions model. Specifically it provides pre-defined > permissions for admin operations (viz. collection-admin and core-admin etc.). > Hence we need an upgrade tool to migrate the existing permissions (written > for Solr 4) to this new permissions model supported by Solr 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1480) A upgrade tool to migrate Solr/Sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1480: Attachment: SENTRY-1480.2.patch > A upgrade tool to migrate Solr/Sentry permissions > -- > > Key: SENTRY-1480 > URL: https://issues.apache.org/jira/browse/SENTRY-1480 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1480.1.patch, SENTRY-1480.2.patch > > > SENTRY-1475 is tracking the integration between Solr 7 and Sentry. Currently > admin privileges for Solr are defined using "admin" as the collection name > (i.e. Sentry reuses collection level permissions for admin operations). > Solr 7, on the other hand, provides a pluggable authorization framework with > fine-grained permissions model. Specifically it provides pre-defined > permissions for admin operations (viz. collection-admin and core-admin etc.). > Hence we need an upgrade tool to migrate the existing permissions (written > for Solr 4) to this new permissions model supported by Solr 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1480) A upgrade tool to migrate Solr/Sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261571#comment-16261571 ] kalyan kumar kalvagadda commented on SENTRY-1480: - [~hgadre] I just attached your latest patch. > A upgrade tool to migrate Solr/Sentry permissions > -- > > Key: SENTRY-1480 > URL: https://issues.apache.org/jira/browse/SENTRY-1480 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1480.1.patch, SENTRY-1480.2.patch > > > SENTRY-1475 is tracking the integration between Solr 7 and Sentry. Currently > admin privileges for Solr are defined using "admin" as the collection name > (i.e. Sentry reuses collection level permissions for admin operations). > Solr 7, on the other hand, provides a pluggable authorization framework with > fine-grained permissions model. Specifically it provides pre-defined > permissions for admin operations (viz. collection-admin and core-admin etc.). > Hence we need an upgrade tool to migrate the existing permissions (written > for Solr 4) to this new permissions model supported by Solr 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1480) A upgrade tool to migrate Solr/Sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262498#comment-16262498 ] kalyan kumar kalvagadda commented on SENTRY-1480: - [~hgadre] Thanks for the contribution. > A upgrade tool to migrate Solr/Sentry permissions > -- > > Key: SENTRY-1480 > URL: https://issues.apache.org/jira/browse/SENTRY-1480 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1480.1.patch, SENTRY-1480.2.patch > > > SENTRY-1475 is tracking the integration between Solr 7 and Sentry. Currently > admin privileges for Solr are defined using "admin" as the collection name > (i.e. Sentry reuses collection level permissions for admin operations). > Solr 7, on the other hand, provides a pluggable authorization framework with > fine-grained permissions model. Specifically it provides pre-defined > permissions for admin operations (viz. collection-admin and core-admin etc.). > Hence we need an upgrade tool to migrate the existing permissions (written > for Solr 4) to this new permissions model supported by Solr 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1480) A upgrade tool to migrate Solr/Sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1480: Resolution: Fixed Status: Resolved (was: Patch Available) > A upgrade tool to migrate Solr/Sentry permissions > -- > > Key: SENTRY-1480 > URL: https://issues.apache.org/jira/browse/SENTRY-1480 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Hrishikesh Gadre >Assignee: Hrishikesh Gadre > Fix For: 2.0.0 > > Attachments: SENTRY-1480.1.patch, SENTRY-1480.2.patch > > > SENTRY-1475 is tracking the integration between Solr 7 and Sentry. Currently > admin privileges for Solr are defined using "admin" as the collection name > (i.e. Sentry reuses collection level permissions for admin operations). > Solr 7, on the other hand, provides a pluggable authorization framework with > fine-grained permissions model. Specifically it provides pre-defined > permissions for admin operations (viz. collection-admin and core-admin etc.). > Hence we need an upgrade tool to migrate the existing permissions (written > for Solr 4) to this new permissions model supported by Solr 7. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENTRY-1998) Create release version 2.1.0 in Jira
[ https://issues.apache.org/jira/browse/SENTRY-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262510#comment-16262510 ] kalyan kumar kalvagadda commented on SENTRY-1998: - [~spena] Thanks for the help in creating the release 2.1.1 in jira. > Create release version 2.1.0 in Jira > > > Key: SENTRY-1998 > URL: https://issues.apache.org/jira/browse/SENTRY-1998 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: release > Fix For: 2.0.0 > > > The next release version after 2.0.0 would be 2.1.0 based. > I'd like to have a new 2.1.0 version on JIRA to move unresolved jira's to it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENTRY-1998) Create release version 2.1.0 in Jira
[ https://issues.apache.org/jira/browse/SENTRY-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda resolved SENTRY-1998. - Resolution: Fixed > Create release version 2.1.0 in Jira > > > Key: SENTRY-1998 > URL: https://issues.apache.org/jira/browse/SENTRY-1998 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: release > Fix For: 2.0.0 > > > The next release version after 2.0.0 would be 2.1.0 based. > I'd like to have a new 2.1.0 version on JIRA to move unresolved jira's to it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENTRY-1998) Create release version 2.1.0 in Jira
[ https://issues.apache.org/jira/browse/SENTRY-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-1998: --- Assignee: kalyan kumar kalvagadda > Create release version 2.1.0 in Jira > > > Key: SENTRY-1998 > URL: https://issues.apache.org/jira/browse/SENTRY-1998 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: release > Fix For: 2.0.0 > > > The next release version after 2.0.0 would be 2.1.0 based. > I'd like to have a new 2.1.0 version on JIRA to move unresolved jira's to it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SENTRY-1999) Sanitize issues that are outstanding for 2.0.0 release
[ https://issues.apache.org/jira/browse/SENTRY-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259857#comment-16259857 ] kalyan kumar kalvagadda edited comment on SENTRY-1999 at 11/22/17 1:26 PM: --- Currently target version is update in below listed jira's. I'm updating them to 2.0.0 ||Key||Summary|| |SENTRY-2058|CLONE - Set hadoop.tmp.dir to the maven build directory configured on java.io.tmpdir| |SENTRY-2047|isTableEmptyCore method in SentryStore has references to MAuthzPathsMapping when it should be generic| |SENTRY-2032|Leading Slashes need to removed when creating HMS path entries| |SENTRY-2031|Add trigger mechanism for Sentry to pull full path snapshot from HMS| |SENTRY-2027|Create mechanism of delivering commands via WebUI| |SENTRY-2014|Incorrect handling of HDFS paths with multiple slashes| |SENTRY-1966|Improve logging of HMS sync data (paths and permissions) flowing from Sentry to NameNode| |SENTRY-1932|Improve logging for HMSPath| |SENTRY-1915|Sentry is doing a lot of work to convert list of paths to HMSPaths structure| |SENTRY-1909|Improvements for memory usage when full path snapshot is sent from Sentry to NN| |SENTRY-1892|Reduce memory consumption of HMSPath$Entry and TPathEntry| |SENTRY-1863|SENTRY-1829 Update Sentry website to reflect 1.8.0 release| |SENTRY-1862|SENTRY-1829 Create 1.8.0 artifacts. sign and upload to sentry package repo| |SENTRY-1853|Add the log level access mechanism| |SENTRY-1852|Refactor HMSFollower without renaming file| |SENTRY-1851|SENTRY-872 Revert HMSFollower refactoring change| |SENTRY-1847|SENTRY-1838 Integrate sentry with Hive 2.0.0| |SENTRY-1843|SENTRY-1838 Fork sentry-binding-hive-follower package to support Hive 2.x| |SENTRY-1825|SENTRY-872 Dropping a Hive database/table doesn't cleanup the permissions associated with it| |SENTRY-1696|SENTRY-872 Expose time spent creating the initial snapshot as a metric| was (Author: kkalyan): Currently target version is update in below listed jira's. I. updating them to 2.0.0 ||Key||Summary|| |SENTRY-2058|CLONE - Set hadoop.tmp.dir to the maven build directory configured on java.io.tmpdir| |SENTRY-2047|isTableEmptyCore method in SentryStore has references to MAuthzPathsMapping when it should be generic| |SENTRY-2032|Leading Slashes need to removed when creating HMS path entries| |SENTRY-2031|Add trigger mechanism for Sentry to pull full path snapshot from HMS| |SENTRY-2027|Create mechanism of delivering commands via WebUI| |SENTRY-2014|Incorrect handling of HDFS paths with multiple slashes| |SENTRY-1966|Improve logging of HMS sync data (paths and permissions) flowing from Sentry to NameNode| |SENTRY-1932|Improve logging for HMSPath| |SENTRY-1915|Sentry is doing a lot of work to convert list of paths to HMSPaths structure| |SENTRY-1909|Improvements for memory usage when full path snapshot is sent from Sentry to NN| |SENTRY-1892|Reduce memory consumption of HMSPath$Entry and TPathEntry| |SENTRY-1863|SENTRY-1829 Update Sentry website to reflect 1.8.0 release| |SENTRY-1862|SENTRY-1829 Create 1.8.0 artifacts. sign and upload to sentry package repo| |SENTRY-1853|Add the log level access mechanism| |SENTRY-1852|Refactor HMSFollower without renaming file| |SENTRY-1851|SENTRY-872 Revert HMSFollower refactoring change| |SENTRY-1847|SENTRY-1838 Integrate sentry with Hive 2.0.0| |SENTRY-1843|SENTRY-1838 Fork sentry-binding-hive-follower package to support Hive 2.x| |SENTRY-1825|SENTRY-872 Dropping a Hive database/table doesn't cleanup the permissions associated with it| |SENTRY-1696|SENTRY-872 Expose time spent creating the initial snapshot as a metric| > Sanitize issues that are outstanding for 2.0.0 release > -- > > Key: SENTRY-1999 > URL: https://issues.apache.org/jira/browse/SENTRY-1999 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: release > Fix For: 2.0.0 > > > Make sure all resolved issues have fix version and make sure all Jiras with > fix version 2.0.0 are committed or moved out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1864) Update the blog with new 1.8.0 features
[ https://issues.apache.org/jira/browse/SENTRY-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1864: Fix Version/s: 1.8.0 > Update the blog with new 1.8.0 features > --- > > Key: SENTRY-1864 > URL: https://issues.apache.org/jira/browse/SENTRY-1864 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Sergio Peña > Fix For: 1.8.0 > > > Need to add a new blob post to publicly announce the Sentry 1.8.0 release. > https://blogs.apache.org/sentry/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2062) Support the new Hive 2.3.2 DbNotificationListener
[ https://issues.apache.org/jira/browse/SENTRY-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2062: Fix Version/s: 2.0.0 > Support the new Hive 2.3.2 DbNotificationListener > - > > Key: SENTRY-2062 > URL: https://issues.apache.org/jira/browse/SENTRY-2062 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Sergio Peña >Assignee: Sergio Peña > Fix For: 2.0.0 > > Attachments: SENTRY-2062.1.patch, SENTRY-2062.2.patch > > > Hive 2.3.2 brings changes to the DbNotificationListener that makes all the > Sentry message events classes incompatible with it. Because > DbNotificationListener is maintained on the Hive side and it may have > improvements in the future, we should switch to it instead of using > SentryMetastorePostEventListenerNotificationLog that is old code from the old > sentry design. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1993) StringIndexOutOfBoundsException in HMSPathsDumper.java
[
https://issues.apache.org/jira/browse/SENTRY-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1993:
Fix Version/s: 2.0.0
> StringIndexOutOfBoundsException in HMSPathsDumper.java
> --
>
> Key: SENTRY-1993
> URL: https://issues.apache.org/jira/browse/SENTRY-1993
> Project: Sentry
> Issue Type: Bug
>Reporter: Misha Dmitriev
>Assignee: Misha Dmitriev
> Fix For: 2.0.0
>
> Attachments: SENTRY-1993.01.patch
>
>
> The following line in HMSPathsDumper.java is causing
> StringIndexOutOfBoundsException:
> {code}
> if (tChildPathElement.charAt(0) == DupDetector.REPLACEMENT_STRING_PREFIX) {
> {code}
> It only happens when a path element is "", when someone mistakenly specifies
> hdfs path with two "/" in the path section, like
> hdfs://server//element1//element2, instead of
> hdfs://server/element1/element2. In principle, such paths are invalid, but
> this code should be made resistant to them anyway.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-2065) Timestamp in MSentryPathChange and MSentryPermChange should be set by DB server
[ https://issues.apache.org/jira/browse/SENTRY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2065: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Timestamp in MSentryPathChange and MSentryPermChange should be set by DB > server > --- > > Key: SENTRY-2065 > URL: https://issues.apache.org/jira/browse/SENTRY-2065 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Na Li >Assignee: Na Li > Fix For: 2.1.0 > > > The timestamp of the path change and perm change entries should be set by DB > server, so when there are multiple sentry servers, the timestamp of the > entries are from the single source, i.e., no need to require the time sync > among sentry servers. When sentry retrieve those entries for HDFS, sentry can > retrieve the entries after the given timestamp from request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-378) Clean up the usage of SentryAccessDeniedException
[ https://issues.apache.org/jira/browse/SENTRY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-378: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Clean up the usage of SentryAccessDeniedException > - > > Key: SENTRY-378 > URL: https://issues.apache.org/jira/browse/SENTRY-378 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Jan Hentschel >Priority: Minor > Fix For: 2.1.0 > > Attachments: SENTRY-378.001.patch, SENTRY-378.002.patch, > SENTRY-378.002.patch, SENTRY-378.003.patch > > > SentryAccessDeniedException is mostly used when user does is not part of > sentry admin group, but is trying to create role, grant role or grant > privilege. Although I see that it is also used else where, there is scope > for some clean up. For example: > SentryStore.getMSentryVersion() -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1568) Develop automated test for client failover
[ https://issues.apache.org/jira/browse/SENTRY-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1568: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Develop automated test for client failover > -- > > Key: SENTRY-1568 > URL: https://issues.apache.org/jira/browse/SENTRY-1568 > Project: Sentry > Issue Type: Bug > Components: Sentry, Test >Affects Versions: 2.0.0 >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Critical > Fix For: 2.1.0 > > > We need a automated test for SENTRY-1477. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-110) Add user's home directory as implied URI access
[ https://issues.apache.org/jira/browse/SENTRY-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-110: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add user's home directory as implied URI access > --- > > Key: SENTRY-110 > URL: https://issues.apache.org/jira/browse/SENTRY-110 > Project: Sentry > Issue Type: New Feature >Reporter: Ben Spivey > Labels: grant/revoke > Fix For: 2.1.0 > > > It would be great if by default users are granted access to their own home > directory (/user/) without having an administrator grant them URI > access. Explicit access does not scale well and requires frequent policy > file changes. Having this feature would allow users to export query results > as files in their home directory on HDFS. > As part of this, there should be a global configuration to disable this > feature. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1877) Add counter for transactions that failed completely
[ https://issues.apache.org/jira/browse/SENTRY-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1877: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add counter for transactions that failed completely > --- > > Key: SENTRY-1877 > URL: https://issues.apache.org/jira/browse/SENTRY-1877 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Alexander Kolbasov >Priority: Minor > Labels: bite-sized, newbie > Fix For: 2.1.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > It is useful to add a metrics counter for the case where TransactionManager > completely fails to execute transactions after all retries. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1819) HMSFollower and friends do not belong in sentry.service.thrift
[
https://issues.apache.org/jira/browse/SENTRY-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1819:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> HMSFollower and friends do not belong in sentry.service.thrift
> --
>
> Key: SENTRY-1819
> URL: https://issues.apache.org/jira/browse/SENTRY-1819
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 2.0.0
>Reporter: Alexander Kolbasov
>Priority: Minor
> Fix For: 2.1.0
>
>
> We have several important classes - e.g. HMSFollower, NotificationProcessor,
> CounterWait, LeaderStatusMonitor in the {{sentry.service.thrift}} package
> which is weird - they should be in {{provider.db.service.persistent}} instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-937) We can get rid of masking logic in getFsPermission of SentryAuthorizationProvider
[ https://issues.apache.org/jira/browse/SENTRY-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-937: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > We can get rid of masking logic in getFsPermission of > SentryAuthorizationProvider > - > > Key: SENTRY-937 > URL: https://issues.apache.org/jira/browse/SENTRY-937 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur >Priority: Minor > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1876) Filter the result of show databases and show tables in hive
[ https://issues.apache.org/jira/browse/SENTRY-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1876: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Filter the result of show databases and show tables in hive > --- > > Key: SENTRY-1876 > URL: https://issues.apache.org/jira/browse/SENTRY-1876 > Project: Sentry > Issue Type: Improvement > Components: Hive Binding >Affects Versions: 1.7.0, 1.8.0, 2.0.0 >Reporter: Yifeng Dong > Fix For: 2.1.0 > > Attachments: SENTRY-1876.002.patch, SENTRY-1876.patch > > > Since now sentry only filter the result of show columns.It's very necessary > to filter the result of show databases and show tables in hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1688) Apache fails to build Sentry package Sentry-jdk-1.7-v2
[
https://issues.apache.org/jira/browse/SENTRY-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1688:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Apache fails to build Sentry package Sentry-jdk-1.7-v2
> ---
>
> Key: SENTRY-1688
> URL: https://issues.apache.org/jira/browse/SENTRY-1688
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Reporter: Alexander Kolbasov
>Assignee: Sergio Peña
>Priority: Minor
> Fix For: 2.1.0
>
>
> For some time Apache job that builds Sentry-jdk-1.7-v2 fails with a rat
> exception in sentry-service-server:
> {code}
> [INFO]
>
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Sentry SUCCESS [16.973s]
> [INFO] Sentry Core ... SUCCESS [2.369s]
> [INFO] Sentry Core Common SUCCESS [1:18.513s]
> [INFO] Sentry Core Model DB .. SUCCESS [7.649s]
> [INFO] Sentry Core Model Indexer . SUCCESS [5.596s]
> [INFO] Sentry Core Model Search .. SUCCESS [5.282s]
> [INFO] Sentry Core Model Sqoop ... SUCCESS [5.448s]
> [INFO] Sentry Core Model Kafka ... SUCCESS [5.676s]
> [INFO] Sentry Service SUCCESS [2.295s]
> [INFO] Sentry Service Common . SUCCESS [14.661s]
> [INFO] Sentry Providers .. SUCCESS [2.751s]
> [INFO] Sentry Provider Common SUCCESS [4.940s]
> [INFO] Sentry Provider File .. SUCCESS [6.453s]
> [INFO] Sentry Service Client . SUCCESS [5.534s]
> [INFO] Sentry Policies ... SUCCESS [2.150s]
> [INFO] Sentry Policy Common .. SUCCESS [10.257s]
> [INFO] Sentry Authorization Provider . SUCCESS [9.241s]
> [INFO] Sentry Service Server . FAILURE
> [10:06.319s]
> [INFO] Sentry Provider DB SUCCESS [5.009s]
> [INFO] Sentry Policy Engine .. SUCCESS [5.334s]
> [INFO] Sentry Bindings ... SUCCESS [2.437s]
> [INFO] Sentry Binding for Kafka .. SUCCESS [20.473s]
> [INFO] Sentry Provider Cache . SUCCESS [7.156s]
> [INFO] Sentry Hive Binding Common SUCCESS [10.143s]
> [INFO] Sentry Binding for Solr ... SUCCESS [19.103s]
> [INFO] Sentry Binding for Sqoop .. SUCCESS [15.041s]
> [INFO] Sentry Binding v2 for Hive SUCCESS [16.203s]
> [INFO] Sentry Policy for Indexer . SUCCESS [17.663s]
> [INFO] Sentry Solr ... SUCCESS [3.083s]
> [INFO] Solr Sentry Core .. SUCCESS [7.723s]
> [INFO] Solr Sentry handler ... SUCCESS [27.111s]
> [INFO] Sentry Tests .. SUCCESS [2.865s]
> [INFO] Sentry Solr Tests . SKIPPED
> [INFO] Sentry Sqoop Tests SKIPPED
> [INFO] Sentry Kafka Tests SKIPPED
> [INFO] Sentry HDFS ... SUCCESS [3.260s]
> [INFO] Sentry HDFS Common SKIPPED
> [INFO] Sentry HDFS Service ... SKIPPED
> [INFO] Sentry HDFS Namenode Plugin ... SKIPPED
> [INFO] Sentry Hive Tests v2 .. SKIPPED
> [INFO] Sentry HDFS Dist .. SKIPPED
> [INFO] Sentry Distribution ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 17:17.124s
> [INFO] Finished at: Sat Apr 01 00:32:51 UTC 2017
> [INFO] Final Memory: 113M/694M
> [INFO]
>
> Waiting for Jenkins to finish collecting data
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.10:check
> (header-check) on project sentry-service-server: Too many fil
[jira] [Updated] (SENTRY-538) Parallel setup sentry service and hiveServer to cut down runtime of sentry-hive-tests
[ https://issues.apache.org/jira/browse/SENTRY-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-538: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Parallel setup sentry service and hiveServer to cut down runtime of > sentry-hive-tests > - > > Key: SENTRY-538 > URL: https://issues.apache.org/jira/browse/SENTRY-538 > Project: Sentry > Issue Type: Improvement >Reporter: Xiaomeng Huang >Priority: Trivial > Fix For: 2.1.0 > > Attachments: SENTRY-538.001.patch > > > Hive e2e tests cost much time to setup sentry service and hiveServer for > every test class. Sentry service and hiveServer don't have dependency and can > multiple thread to setup. If it makes you comfortable, it can cut down the > runtime obviously. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1679) HDFS tests configure MetastorePlugin which is gone
[
https://issues.apache.org/jira/browse/SENTRY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1679:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> HDFS tests configure MetastorePlugin which is gone
> --
>
> Key: SENTRY-1679
> URL: https://issues.apache.org/jira/browse/SENTRY-1679
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 2.0.0
>Reporter: Alexander Kolbasov
>Assignee: Arjun Mishra
>Priority: Minor
> Labels: bite-sized, newbie
> Fix For: 2.1.0
>
>
> In TestHDFSIntegrationBase#startHiveAndMetastore() there is:
> {code}
> hiveConf.set("sentry.metastore.plugins",
> "org.apache.sentry.hdfs.MetastorePlugin");
> {code}
> But we no longer have {{MetastorePlugin}}, so this should be removed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-649) Add e2e tests for Sentry HA with HDFS
[ https://issues.apache.org/jira/browse/SENTRY-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-649: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add e2e tests for Sentry HA with HDFS > - > > Key: SENTRY-649 > URL: https://issues.apache.org/jira/browse/SENTRY-649 > Project: Sentry > Issue Type: Sub-task >Reporter: Prasad Mujumdar >Assignee: Prasad Mujumdar > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-686) fix DB2 database script for sentry metadata
[ https://issues.apache.org/jira/browse/SENTRY-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-686: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > fix DB2 database script for sentry metadata > --- > > Key: SENTRY-686 > URL: https://issues.apache.org/jira/browse/SENTRY-686 > Project: Sentry > Issue Type: Bug >Reporter: shenguoquan >Assignee: shenguoquan > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-582) Cache the gauges (metrics) exposed by Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-582: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Cache the gauges (metrics) exposed by Sentry service > > > Key: SENTRY-582 > URL: https://issues.apache.org/jira/browse/SENTRY-582 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1429) TestHDFSIntegration improvements
[ https://issues.apache.org/jira/browse/SENTRY-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1429: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > TestHDFSIntegration improvements > > > Key: SENTRY-1429 > URL: https://issues.apache.org/jira/browse/SENTRY-1429 > Project: Sentry > Issue Type: Test > Components: Sentry, Test >Affects Versions: 1.8.0, 2.0.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > Attachments: SENTRY-1429.001-sentry-ha-redesign.patch > > > There are a few problems with this test that would be good to fix: > 1. NN pulls the Sentry acls periodically, which means tests cannot verify > acls as soon as it sets up the required privileges. This requires having > sleeps in the test but it leads to some flakyness. We need to make sure we > are actually sleeping after setting the permissions and before veryfying. Or > explore other options to make this robust. > 2. We need to make the tests more granular. There is a bunch of stuff > happening in a single test, so it is hard to pinpoint why a test failed > without looking at the stacktrace and debugging further. > 3. Fix inter test dependencies if any. I see that some tests pass if run > alone, but fail when the entire test class is run, so there might be some > dependencies which we need to clean up. > 4. Make these tests runnable on real cluster. So that we can catch any > integration and configuration issues. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-322) Add tests for rest of the hive operations
[ https://issues.apache.org/jira/browse/SENTRY-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-322: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add tests for rest of the hive operations > - > > Key: SENTRY-322 > URL: https://issues.apache.org/jira/browse/SENTRY-322 > Project: Sentry > Issue Type: Test >Affects Versions: 1.3.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > We need to add test coverage for the following hive commands: > HiveOperation.ALTERPARTITION_SERIALIZER > HiveOperation.ALTERTBLPART_SKEWED_LOCATION > HiveOperation.ALTERTABLE_ARCHIVE > HiveOperation.ALTERTABLE_UNARCHIVE > HiveOperation.ALTERTABLE_SERIALIZER > HiveOperation.ALTERINDEX_PROPS > HiveOperation.ALTERVIEW_PROPERTIES > HiveOperation.LOCKTABLE > HiveOperation.UNLOCKTABLE > HiveOperation.CREATEFUNCTION > HiveOperation.DROPFUNCTION > HiveOperation.SHOW_TABLESTATUS > We also need to make sure we have tests for these: > Explain > DESCFUNCTION > MSCK > ALTER TABLE MERGE FILE > ALTER PARTITION MERGE FILE > ALTER TABLE SKEWED > TRANSFORM > ADD JAR (should not be allowed) > SHOW FUNCTIONs (Not restricted) > SHOW LOCKS(Not Restricted ) > SHOW table extended > Describe table on a view -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1708) Extend the current test classes to handle multiple sentry servers
[ https://issues.apache.org/jira/browse/SENTRY-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1708: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Extend the current test classes to handle multiple sentry servers > - > > Key: SENTRY-1708 > URL: https://issues.apache.org/jira/browse/SENTRY-1708 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: test > Fix For: 2.1.0 > > Attachments: SENTRY-1708.001-sentry-ha-redesign.patch, > SENTRY-1708.002-sentry-ha-redesign.patch, > SENTRY-1708.003-sentry-ha-redesign.patch, > SENTRY-1708.004-sentry-ha-redesign.patch, > SENTRY-1708.005-sentry-ha-redesign.patch, > SENTRY-1708.006-sentry-ha-redesign.patch, > SENTRY-1708.007-sentry-ha-redesign.patch, > SENTRY-1708.008-sentry-ha-redesign.patch, > SENTRY-1708.009-sentry-ha-redesign.patch, > SENTRY-1708.010-sentry-ha-redesign.patch > > > we need to extend the base classes like SentryServiceIntegrationBase which is > used my a lot tests to work with multiple sentry servers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-773) Granting on table and revoking on column does not work
[ https://issues.apache.org/jira/browse/SENTRY-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-773: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Granting on table and revoking on column does not work > -- > > Key: SENTRY-773 > URL: https://issues.apache.org/jira/browse/SENTRY-773 > Project: Sentry > Issue Type: New Feature >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > "grant select on table" followed by "revoke select(a) on table" does not work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1775) Unit test for HMSFollower is not testing anything useful
[
https://issues.apache.org/jira/browse/SENTRY-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1775:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Unit test for HMSFollower is not testing anything useful
>
>
> Key: SENTRY-1775
> URL: https://issues.apache.org/jira/browse/SENTRY-1775
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 2.0.0
>Reporter: Alexander Kolbasov
>Assignee: kalyan kumar kalvagadda
> Labels: test
> Fix For: 2.1.0
>
>
> The unit test for HMSFollower was broken - it used incorrect hdfs path
> {{hdfs://db1}} which was causing exception during parsing. This test only
> checks for calls to SentryStore but doesn't actually verify updates created.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-22) Create built in documentation
[ https://issues.apache.org/jira/browse/SENTRY-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-22: -- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Create built in documentation > - > > Key: SENTRY-22 > URL: https://issues.apache.org/jira/browse/SENTRY-22 > Project: Sentry > Issue Type: Improvement >Reporter: Shreepadma Venugopalan > Fix For: 2.1.0 > > > We need to create documentation for Sentry. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-983) Test that all collection request handlers are protected
[ https://issues.apache.org/jira/browse/SENTRY-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-983: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Test that all collection request handlers are protected > --- > > Key: SENTRY-983 > URL: https://issues.apache.org/jira/browse/SENTRY-983 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 2.1.0 > > > As of today we verify individual handlers but don't verify that all > collection handlers are protected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-93) let sentry-solr-binding hand off to solr for hdfs authentication
[ https://issues.apache.org/jira/browse/SENTRY-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-93: -- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > let sentry-solr-binding hand off to solr for hdfs authentication > > > Key: SENTRY-93 > URL: https://issues.apache.org/jira/browse/SENTRY-93 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 2.1.0 > > Attachments: SENTRY-93.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-240) Handle active roles in the hive binding and get rid of hive specific sentry thrift api
[
https://issues.apache.org/jira/browse/SENTRY-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-240:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Handle active roles in the hive binding and get rid of hive specific sentry
> thrift api
> --
>
> Key: SENTRY-240
> URL: https://issues.apache.org/jira/browse/SENTRY-240
> Project: Sentry
> Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Sravya Tirukkovalur
> Fix For: 2.1.0
>
>
> Would be good to get rid of maintaining active role set struct and
> list_sentry_privileges_for_provider in thrift
> I think we should handle active roles on hive side outside of sentry service,
> as we do not really store these mappings in the db. And does not make sense
> to store these in db as these are per session variables. If we do this, we
> can clean up the thrift interface a bit and just have:
> TListSentryPrivilegesResponse
> list_sentry_privileges(1:TListSentryPrivilegesRequest request)
> struct TListSentryPrivilegesRequest {
> 1: required i32 protocol_version = sentry_common_service.TSENTRY_SERVICE_V1,
> 2: required string requestorUserName, # user on whose behalf the request is
> issued
> 3: required set roleNames # get privileges assigned for this role
> 4: optional TSentryAuthorizable authorizableHierarchy
> }
> And do the set intersection of rolesforGroup and active roles in the hive
> binding itself.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-756) Blacklist columns instead of whitelist in column level privileges
[ https://issues.apache.org/jira/browse/SENTRY-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-756: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Blacklist columns instead of whitelist in column level privileges > - > > Key: SENTRY-756 > URL: https://issues.apache.org/jira/browse/SENTRY-756 > Project: Sentry > Issue Type: New Feature >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 2.1.0 > > > This would decrease the size of data for wide tables as #columns restricted > is usually < # columns allowed access. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-270) URI seems to be case insensitive when using policy files
[ https://issues.apache.org/jira/browse/SENTRY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-270: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > URI seems to be case insensitive when using policy files > > > Key: SENTRY-270 > URL: https://issues.apache.org/jira/browse/SENTRY-270 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.3.0 >Reporter: Sravya Tirukkovalur > Labels: grant/revoke > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1930) Switch to hive-authz2 profile by default
[ https://issues.apache.org/jira/browse/SENTRY-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1930: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Switch to hive-authz2 profile by default > > > Key: SENTRY-1930 > URL: https://issues.apache.org/jira/browse/SENTRY-1930 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Sergio Peña >Assignee: Sergio Peña > Fix For: 2.1.0 > > Attachments: SENTRY-1930.1.patch > > > Before removing Hive 1.x (HIVE-1899), we should switch to hive-authz2 profile > to build and test the new Sentry master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1267) Improve skipSlowAndNotThreadSafeTests blacklist/whitelist
[ https://issues.apache.org/jira/browse/SENTRY-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1267: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Improve skipSlowAndNotThreadSafeTests blacklist/whitelist > - > > Key: SENTRY-1267 > URL: https://issues.apache.org/jira/browse/SENTRY-1267 > Project: Sentry > Issue Type: Improvement > Components: Test >Affects Versions: 1.8.0 >Reporter: Gregory Chanan > Fix For: 2.1.0 > > > We currently explicitly exclude certain non thread safe tests: > https://github.com/apache/sentry/blob/2109f42945cb132c4bf738649abf2935288d1e20/pom.xml#L897-L903 > Though it's nice that this list is in one place, this is unmaintainable as we > add more tests. The usual way of solving this is to define annotations > around the tests that define when they should run. E.g. in this case, there > are a bunch of non-thread safe tests that derive from > SentryGenericServiceIntegrationBase. We can just annotate this base class > with @NonThreadSafe or something, which will be less of a maintenance > headache. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1117) solr-sentry-handlers and solr-sentry-core should be renamed to sentry-solr
[
https://issues.apache.org/jira/browse/SENTRY-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1117:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> solr-sentry-handlers and solr-sentry-core should be renamed to sentry-solr
> --
>
> Key: SENTRY-1117
> URL: https://issues.apache.org/jira/browse/SENTRY-1117
> Project: Sentry
> Issue Type: Task
> Components: Solr Plugin
>Reporter: Gregory Chanan
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.1.0
>
> Attachments: SENTRY-1117.001-sentry-ha-redesign.patch,
> SENTRY-1117.001.patch
>
>
> This specification is inconsistent with the sentry-hdfs plugin:
> {code}
> ~/workspace/incubator-sentry8/sentry-hdfs$ ls
> pom.xml sentry-hdfs-dist sentry-hdfs-service
> sentry-hdfs-common sentry-hdfs-namenode-plugin target
> {code}
> {code}
> :~/workspace/incubator-sentry8/sentry-solr$ ls
> pom.xml solr-sentry-core solr-sentry-handlers target
> {code}
> i.e. solr-sentry-core and solr-sentry-handlers should be sentry-solr-core and
> sentry-solr-handlers, respectively.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-1761) Add test for concurrent HMS followers processing notifications
[ https://issues.apache.org/jira/browse/SENTRY-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1761: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add test for concurrent HMS followers processing notifications > -- > > Key: SENTRY-1761 > URL: https://issues.apache.org/jira/browse/SENTRY-1761 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Fix For: 2.1.0 > > Attachments: SENTRY-1761.001-sentry-ha-redesign.patch, > SENTRY-1761.002-sentry-ha-redesign.patch, > SENTRY-1761.003-sentry-ha-redesign.patch, > SENTRY-1761.004-sentry-ha-redesign.patch > > > Added test to make sure that SENTRY_HMS_NOTIFICATION_ID table is properly > updated even when multiple HMSFollowers are processing notifications from HMS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-395) Support wildcard support in privileges
[ https://issues.apache.org/jira/browse/SENTRY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-395: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Support wildcard support in privileges > -- > > Key: SENTRY-395 > URL: https://issues.apache.org/jira/browse/SENTRY-395 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > As a follow on to Sentry-74. > Supporting this is even more important after we support column level > privileges. It's more likely that a user is blocked access a small subset of > the columns to protect some sensitive data while allow access to the rest. > So would be good to support wildcard characters, so that users can > selectively grant access. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1223) Add validator for authorization type hierarchy
[ https://issues.apache.org/jira/browse/SENTRY-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1223: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add validator for authorization type hierarchy > -- > > Key: SENTRY-1223 > URL: https://issues.apache.org/jira/browse/SENTRY-1223 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 2.1.0 > > Attachments: SENTRY-1223.001.patch > > > Currently, SimpleFileProviderBackend is responsible for parse .ini file, but > the file provider backend is deprecated. The logic for parse .ini file and > validate authorization type hierarchy should be separated from > SimpleFileProviderBackend. This JIRA is for adding authorization type > hierarchy validator. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-874) Handle HMS updates correctly while full update is being built
[ https://issues.apache.org/jira/browse/SENTRY-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-874: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Handle HMS updates correctly while full update is being built > - > > Key: SENTRY-874 > URL: https://issues.apache.org/jira/browse/SENTRY-874 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > We have two options here: > 1. Have a lock for path update + notify sentry. So that a partial update > would just block until the full update completes building and notifying > Sentry. > 2. Make sure path update duplicates are handled well in HMSPaths and > SentryPlugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-298) Save the current database and switch back to it while granting privileges in db provider tests
[ https://issues.apache.org/jira/browse/SENTRY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-298: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Save the current database and switch back to it while granting privileges in > db provider tests > -- > > Key: SENTRY-298 > URL: https://issues.apache.org/jira/browse/SENTRY-298 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Priority: Minor > Labels: grant/revoke > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1787) Remove use of unnecessary SentryMetastorePostEventListenerNotificationLog class
[ https://issues.apache.org/jira/browse/SENTRY-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1787: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Remove use of unnecessary SentryMetastorePostEventListenerNotificationLog > class > --- > > Key: SENTRY-1787 > URL: https://issues.apache.org/jira/browse/SENTRY-1787 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Sergio Peña >Assignee: Venkatesh Ramasamy >Priority: Minor > Labels: bite-sized, newbie > Fix For: 2.1.0 > > Attachments: SENTRY-1787.001.patch, > SENTRY-1787.01-sentry-ha-redesign.patch, > SENTRY-1787.02-sentry-ha-redesign.patch > > > The SentryMetastorePostEventListenerNotificationLog class is not used anymore > on Sentry. We should remove this from the codebase. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-940) Drop table should revert the user:group rules of the directory and underlying files to original hdfs rules
[ https://issues.apache.org/jira/browse/SENTRY-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-940: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Drop table should revert the user:group rules of the directory and underlying > files to original hdfs rules > -- > > Key: SENTRY-940 > URL: https://issues.apache.org/jira/browse/SENTRY-940 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Ryan P > Fix For: 2.1.0 > > > Note that, the directory is created first before creating a table, so the > original user can be different from hive:hive -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-379) Db entities are not captured when firing failurehook for SentryAccessDeniedException
[
https://issues.apache.org/jira/browse/SENTRY-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-379:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Db entities are not captured when firing failurehook for
> SentryAccessDeniedException
>
>
> Key: SENTRY-379
> URL: https://issues.apache.org/jira/browse/SENTRY-379
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: Sravya Tirukkovalur
>Priority: Minor
> Fix For: 2.1.0
>
>
> {noformat}
> SentryOnFailureHookContext hookContext = new SentryOnFailureHookContextImpl(
> queryPlan.getQueryString(), new HashSet(),
> new HashSet(), stmtOperation,
> null, null, null, null, subject.getName(), ipAddress,
> new AuthorizationException(e), conf);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-1204) Add method to enforce validator when creating the privileges if possible
[ https://issues.apache.org/jira/browse/SENTRY-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1204: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add method to enforce validator when creating the privileges if possible > > > Key: SENTRY-1204 > URL: https://issues.apache.org/jira/browse/SENTRY-1204 > Project: Sentry > Issue Type: Improvement >Reporter: Colin Ma >Assignee: Colin Ma > Fix For: 2.1.0 > > > A new method createValidatedPrivilege() can be added to PrivilegeFactory, and > add validate(List) method to Privilege. Then Privilege > can be validated during the creation if necessary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-896: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > 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: 2.1.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.4.14#64029)
[jira] [Updated] (SENTRY-242) All command line parameters not recognizable by Sentry Main should come at the end.
[ https://issues.apache.org/jira/browse/SENTRY-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-242: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > All command line parameters not recognizable by Sentry Main should come at > the end. > --- > > Key: SENTRY-242 > URL: https://issues.apache.org/jira/browse/SENTRY-242 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Priority: Minor > Labels: grant/revoke > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-386) Provide a default log4j file for Sentry service which logs to the console
[ https://issues.apache.org/jira/browse/SENTRY-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-386: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Provide a default log4j file for Sentry service which logs to the console > - > > Key: SENTRY-386 > URL: https://issues.apache.org/jira/browse/SENTRY-386 > Project: Sentry > Issue Type: Task >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Priority: Minor > Labels: newbie > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-754) Support column level privileges on views
[ https://issues.apache.org/jira/browse/SENTRY-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-754: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Support column level privileges on views > > > Key: SENTRY-754 > URL: https://issues.apache.org/jira/browse/SENTRY-754 > Project: Sentry > Issue Type: New Feature > Components: Hive Plugin >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-497) Sentry Web UI
[ https://issues.apache.org/jira/browse/SENTRY-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-497: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Sentry Web UI > - > > Key: SENTRY-497 > URL: https://issues.apache.org/jira/browse/SENTRY-497 > Project: Sentry > Issue Type: New Feature >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > Jamon looks like a good candidate, HBase recently switched to Jamon > [HBASE-3835| https://issues.apache.org/jira/browse/HBASE-3835] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1588) Add user level privilege change support for SentryPolicyStorePlugin
[ https://issues.apache.org/jira/browse/SENTRY-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1588: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add user level privilege change support for SentryPolicyStorePlugin > --- > > Key: SENTRY-1588 > URL: https://issues.apache.org/jira/browse/SENTRY-1588 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 2.0.0 >Reporter: Hao Hao >Priority: Critical > Labels: hdfs-sync, merge > Fix For: 2.1.0 > > > Discovered user level privilege support for SentryPolicyStorePlugin is > missing during working on SENTRY-1536. As SENTRY-711 introduced user level > privilege, corresponding permission change should be captured for > SentryPolicyStorePlugin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2067) Refactor HMS Follower syncupWithHms method
[ https://issues.apache.org/jira/browse/SENTRY-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2067: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Refactor HMS Follower syncupWithHms method > -- > > Key: SENTRY-2067 > URL: https://issues.apache.org/jira/browse/SENTRY-2067 > Project: Sentry > Issue Type: Bug > Components: Sentry >Reporter: Arjun Mishra >Assignee: Arjun Mishra > Labels: bite-sized > Fix For: 2.1.0 > > > Currently we seem to be getting a full snapshot even when HDFS Sync is > disabled. A full snapshot can be very time consuming and puts a lot of strain > on resources and it doesn't make sense to have to get it without persisting > it. Code needs to be refactored to handle all cases with HDFS Sync enabled > and disabled appropriately -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1167) Add new properties for SSL in the wiki
[ https://issues.apache.org/jira/browse/SENTRY-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1167: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add new properties for SSL in the wiki > -- > > Key: SENTRY-1167 > URL: https://issues.apache.org/jira/browse/SENTRY-1167 > Project: Sentry > Issue Type: Sub-task >Reporter: Li Li >Assignee: Li Li > Fix For: 2.1.0 > > > Add the following properties for SSL into the > [wiki|https://cwiki.apache.org/confluence/display/SENTRY/Sentry+Service+Configuration]: > sentry.web.use.ssl > sentry.web.ssl.keystore.path > sentry.web.ssl.keystore.password > sentry.ssl.protocol.blacklist -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-908) Publish Sentry - HDFS sync design spec to wiki
[ https://issues.apache.org/jira/browse/SENTRY-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-908: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Publish Sentry - HDFS sync design spec to wiki > -- > > Key: SENTRY-908 > URL: https://issues.apache.org/jira/browse/SENTRY-908 > Project: Sentry > Issue Type: Task > Components: Hdfs Plugin >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Labels: Docs > Fix For: 2.1.0 > > > It would be helpful to list out the feature in detail. Different > configuration options that we have to fine tune etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-104) Require URI for all custom classes
[ https://issues.apache.org/jira/browse/SENTRY-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-104: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Require URI for all custom classes > -- > > Key: SENTRY-104 > URL: https://issues.apache.org/jira/browse/SENTRY-104 > Project: Sentry > Issue Type: Improvement >Reporter: Brock Noland >Priority: Critical > Fix For: 2.1.0 > > > At present we require URI for UDFs. We should require URI for any custom > class such as input format, serde, storage handler, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-330) Update Derby schema script to enforce non-null constraint
[ https://issues.apache.org/jira/browse/SENTRY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-330: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Update Derby schema script to enforce non-null constraint > - > > Key: SENTRY-330 > URL: https://issues.apache.org/jira/browse/SENTRY-330 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Prasad Mujumdar > Labels: newbie > Fix For: 2.1.0 > > Attachments: SENTRY-330.patch > > > Currently Derby schema script is not consistent with setting bunch of columns > as non-null. We need to keep this in sync with other schema scripts. Since > derby is used for unit test, this can cause issues to got through unit tests > and fail in the real deployments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1875) Column level privileges should not be stored in the delta tables
[ https://issues.apache.org/jira/browse/SENTRY-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1875: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Column level privileges should not be stored in the delta tables > > > Key: SENTRY-1875 > URL: https://issues.apache.org/jira/browse/SENTRY-1875 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Alexander Kolbasov >Assignee: Na Li > Fix For: 2.1.0 > > > The permission deltas are used for the NameNode synchronization. NameNode > doesn't deal with column-level privileges, so there is no need to store these > in the delta tables. This is a perf optimization in cases when lots of > column-level privileges are used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1075) Uber jira for Sentry Service webpage
[ https://issues.apache.org/jira/browse/SENTRY-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1075: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Uber jira for Sentry Service webpage > > > Key: SENTRY-1075 > URL: https://issues.apache.org/jira/browse/SENTRY-1075 > Project: Sentry > Issue Type: Improvement >Reporter: Li Li >Assignee: Li Li > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1424) Sentry HA client tests: master jira for all client related tests (retry, concurrency, correct exceptions etc.)
[ https://issues.apache.org/jira/browse/SENTRY-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1424: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Sentry HA client tests: master jira for all client related tests (retry, > concurrency, correct exceptions etc.) > -- > > Key: SENTRY-1424 > URL: https://issues.apache.org/jira/browse/SENTRY-1424 > Project: Sentry > Issue Type: Bug > Components: Sentry, Test >Reporter: Anne Yu >Assignee: kalyan kumar kalvagadda > Fix For: 2.1.0 > > > 1. client can connect to active; > 2. client can retry; > 3. multiple clients can concurrent connect; > 4. client can retry until find one active server; > 5. client throws correct exceptions; > 6. test pool client, not sure about the old client apis ? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2064) Sentry client at HDFS should send back the timestamp in last response
[ https://issues.apache.org/jira/browse/SENTRY-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2064: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Sentry client at HDFS should send back the timestamp in last response > - > > Key: SENTRY-2064 > URL: https://issues.apache.org/jira/browse/SENTRY-2064 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Reporter: Na Li >Assignee: Na Li > Fix For: 2.1.0 > > > When sentry server sends response to HDFS, it includes the timestamp of the > current time at the DB server. > When sentry client at HDFS gets response from sentry, it sets its local > variable, which is the latest timestamp received from sentry, to be the > timestamp in the response > When sentry client sends request, it should include the latest timestamp > received from sentry in the request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-581) Collect additional perf metrics for Sentry/HDFS integration
[ https://issues.apache.org/jira/browse/SENTRY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-581: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Collect additional perf metrics for Sentry/HDFS integration > --- > > Key: SENTRY-581 > URL: https://issues.apache.org/jira/browse/SENTRY-581 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Assignee: Prasad Mujumdar > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-410) Some negative test cases do not check for specific Sentry exceptions
[
https://issues.apache.org/jira/browse/SENTRY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-410:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Some negative test cases do not check for specific Sentry exceptions
>
>
> Key: SENTRY-410
> URL: https://issues.apache.org/jira/browse/SENTRY-410
> Project: Sentry
> Issue Type: Test
>Affects Versions: 1.4.0
>Reporter: Sravya Tirukkovalur
> Fix For: 2.1.0
>
>
> in Context.java:
> {noformat}
> // verify that the sqlexception is due to authorization failure
> public void verifyAuthzException(SQLException sqlException) throws
> SQLException{
> verifyAuthzExceptionForState(sqlException, AUTHZ_EXCEPTION_SQL_STATE);
> }
> {noformat}
> This just checks for status 42000, which would also be the case for other
> failures other than SemanticExceptions. We need to make stronger checks in
> the tests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-1049) Use existing validators in hive shell. Automatically for external generic services?
[ https://issues.apache.org/jira/browse/SENTRY-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1049: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Use existing validators in hive shell. Automatically for external generic > services? > > > Key: SENTRY-1049 > URL: https://issues.apache.org/jira/browse/SENTRY-1049 > Project: Sentry > Issue Type: Improvement > Components: Service >Affects Versions: 1.7.0 >Reporter: Gregory Chanan > Fix For: 2.1.0 > > > SENTRY-1047 uses the existing validators for the Solr Shell. We should do > two things in addition to this: > 1) Update the hive shell to use the existing validators > 2) Figure out how arbitrary external generic services can apply their > validations. Can we do that automatically? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1855) Improve scalability of permission delta updates
[
https://issues.apache.org/jira/browse/SENTRY-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1855:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Improve scalability of permission delta updates
> ---
>
> Key: SENTRY-1855
> URL: https://issues.apache.org/jira/browse/SENTRY-1855
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 2.0.0
>Reporter: Alexander Kolbasov
>Assignee: Na Li
> Fix For: 2.1.0
>
> Attachments: SENTRY-1855.001.patch,
> SENTRY-1855.002-sentry-ha-redesign.patch, SENTRY-1855.002.patch,
> SENTRY-1855.003-master.patch, SENTRY-1855.01-sentry-ha-redesign.patch
>
>
> Looking at the latest stress runs, we noticed that some of the transactions
> could fail to commit to the database (with Duplicate key exception) after
> exhausting all the retries.
> This problem has become more evident if we have more number of clients
> connecting to Sentry to issue the permission updates. Was able to reproduce
> consistently with 15 clients doing 100 operations each.
> In the past we introduced exponential backoff (SENTRY-1821) so as part of
> test run increased the defaults to 750ms sleep and 20 retries. But even after
> this, the cluster still shows up the transaction failures. This change also
> increases the latency of every transaction in sentry.
> We need to revisit this and come up with a better way to solve this problem.
> {code}
> 2017-07-13 13:18:14,449 ERROR
> org.apache.sentry.provider.db.service.persistent.TransactionManager: The
> transaction has reached max retry number, Exception thrown when executing
> query
> javax.jdo.JDOException: Exception thrown when executing query
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:596)
> at org.datanucleus.api.jdo.JDOQuery.execute(JDOQuery.java:252)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.getRole(SentryStore.java:294)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.alterSentryRoleGrantPrivilegeCore(SentryStore.java:645)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.access$500(SentryStore.java:101)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore$11.execute(SentryStore.java:601)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransaction(TransactionManager.java:159)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager.access$100(TransactionManager.java:63)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager$2.call(TransactionManager.java:213)
> --
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:971)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2530)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1907)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2141)
> at
> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1773)
> ... 33 more
> 2017-07-13 13:18:14,450 ERROR
> org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor:
> Unknown error for request:
> TAlterSentryRoleGrantPrivilegeRequest(protocol_version:2,
> requestorUserName:hive, roleName:2017_07_12_15_06_38_1_2_805,
> privileges:[TSentryPrivilege(privilegeScope:DATABASE, serverName:server1,
> dbName:2017_07_12_15_06_38_1_2, tableName:, URI:, action:*,
> createTime:1499904401222, grantOption:FALSE, columnName:)]), message: The
> transaction has reached max retry number, Exception thrown when executing
> query
> java.lang.Exception: The transaction has reached max retry number, Exception
> thrown when executing query
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager$ExponentialBackoff.execute(TransactionManager.java:255)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransactionBlocksWithRetry(TransactionManager.java:209)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.execute(SentryStore.java:3330)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.alterSentryRoleGrantPrivilege(SentryStore.java:59
[jira] [Updated] (SENTRY-1813) LeaderStatusMonitor could get into limbo state upon ZK connection loss
[
https://issues.apache.org/jira/browse/SENTRY-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1813:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> LeaderStatusMonitor could get into limbo state upon ZK connection loss
> --
>
> Key: SENTRY-1813
> URL: https://issues.apache.org/jira/browse/SENTRY-1813
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Vamsee Yarlagadda
>Assignee: Vamsee Yarlagadda
> Fix For: 2.1.0
>
> Attachments: Screenshot.png
>
>
> I noticed that during failover testing, if there was a connection loss with
> ZK to the sentry servers, the one who is currently the leader gets into a
> limbo state as it interrupts the Curator-LeaderSelector thread which no
> longer gets revived in the running Sentry process (unless the process is
> restarted).
> Relevant code under LeaderStatusMonitor
> http://github.mtv.cloudera.com/CDH/sentry/blob/cdh5-1.5.1/sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/LeaderStatusMonitor.java#L243-L246
> {code}
>try {
> isLeader = true;
> // Wait until we are interrupted or receive a signal
> cond.await();
> } catch (InterruptedException ignored) {
> Thread.currentThread().interrupt();
> LOG.info("LeaderStatusMonitor: interrupted");
> } finally {
> isLeader = false;
> lock.unlock();
> LOG.info("LeaderStatusMonitor: becoming standby");
> }
> {code}
> I realized even upon the loss of ZK connection, curator framework raises an
> Interrupted Exception in LeaderStausMonitor which attempts to call interrupt
> on Thread.currentThread which is essentially *Curator-LeaderSelector* thread.
>
> So if the LeaderSelector thread is interrupted, this particular Sentry server
> loses the capability of participating in a leader election in the future. And
> if this happens to all the sentry servers in the cluster, any further loss
> could get into a limbo state.
> And during this state, Sentry no longer reads events from HMS and thereby
> users can no longer be able to issue DDL statements like CREATE etc. However
> GRANT, REVOKE still work as they don't go through HMSFollower.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-939) Provide a configuration to be able to fall back to orginal HDFS user:group when NN has stale sentry permissions
[ https://issues.apache.org/jira/browse/SENTRY-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-939: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Provide a configuration to be able to fall back to orginal HDFS user:group > when NN has stale sentry permissions > --- > > Key: SENTRY-939 > URL: https://issues.apache.org/jira/browse/SENTRY-939 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 2.1.0 > > > Seems like some sentry users have a batch id for each application which > creates the directory, ingests the data, then creates a table/partition over > it. So the batch id is the the original owner of this directory. > When NN has stale permissions during the time it cannot talk to Sentry (if > sentry is down), falling back to hive:hive blocks everyone it would be > helpful if at least this batch id has access otherwise ingest pipelines may > break during this time. So would be helpful to provide a way to configure > this behavior. > - This does not entail ACLS. > - We should add hive:hive as acl to make sure hive has access -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1947) Leverage Current Roles to speed up requests for privileges
[ https://issues.apache.org/jira/browse/SENTRY-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1947: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Leverage Current Roles to speed up requests for privileges > -- > > Key: SENTRY-1947 > URL: https://issues.apache.org/jira/browse/SENTRY-1947 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Arjun Mishra >Assignee: Arjun Mishra >Priority: Minor > Fix For: 2.1.0 > > > Right now when roles a re set current, we do nothing to optimize requesting > for privileges. We basically get all roles, and then use the intersection to > further filter the roles. After which we get privileges. > There should be a better approach to this. We should simply use those current > roles, and return privileges for them. We don't even need to check if the > current roles belong to the user-groups because that is something that > should've been checked earlier when making roles current -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-226) Allow adding role:groups/ role:privileges mapping in one RPC
[
https://issues.apache.org/jira/browse/SENTRY-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-226:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Allow adding role:groups/ role:privileges mapping in one RPC
>
>
> Key: SENTRY-226
> URL: https://issues.apache.org/jira/browse/SENTRY-226
> Project: Sentry
> Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Sravya Tirukkovalur
> Fix For: 2.1.0
>
>
> For role:groups:
> Currently although we support this at RPC level:
> alter_sentry_role_add_groups(requestorUserName,requestorGroupNames,
> roleName,groups)
> We do not support this at the SentryServiceClient level:
> public void grantRoleToGroup(String requestorUserName, Set
> requestorUserGroupName,
> String groupName, String roleName)
> For role:privileges:
> Currently we do not support this at the RPC level:
> struct TAlterSentryRoleGrantPrivilegeRequest {
> 1: required i32 protocol_version = sentry_common_service.TSENTRY_SERVICE_V1,
> 2: required string requestorUserName, # user on whose behalf the request is
> issued
> 3: required set requestorGroupNames # groups the requesting user
> belongs to
> 4: required string roleName,
> 5: required TSentryPrivilege privilege
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-679) Sentry support for Hive 0.14 Insert into table table_name values (...)
[
https://issues.apache.org/jira/browse/SENTRY-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-679:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Sentry support for Hive 0.14 Insert into table table_name values (...)
> --
>
> Key: SENTRY-679
> URL: https://issues.apache.org/jira/browse/SENTRY-679
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Anne Yu
>Assignee: Prasad Mujumdar
> Fix For: 2.1.0
>
>
> {code}
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'drop role insert_table'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'CREATE ROLE insert_table'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'GRANT INSERT ON TABLE test2 to ROLE insert_table'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'GRANT ROLE insert_table TO GROUP hive'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'GRANT SELECT ON TABLE t1 to role insert_table'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'SET ROLE insert_table' -e 'insert into table test2
> select * from t1'
> ++ sudo -u hive beeline --color --silent=true -u
> 'jdbc:hive2://anneyu-sentry-ha-10-4.ent.cloudera.com:1/default;principal=hive/anneyu-sentry-ha-10-4.ent.cloudera@ent.cloudera.com'
> -n hive -p hive -e 'SET ROLE insert_table' -e 'insert into table test2
> values ('\''test'\'')'
> Error: Error while compiling statement: FAILED: SemanticException No valid
> privileges
> Required privileges for this query:
> Server=server1->Db=default->Table=values__tmp__table__1->action=select;
> (state=42000,code=4)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.
[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add e2e tests for testing HMS notification processing. > -- > > Key: SENTRY-2034 > URL: https://issues.apache.org/jira/browse/SENTRY-2034 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.0.0 >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Fix For: 2.1.0 > > Attachments: SENTRY-2034.001.patch, SENTRY-2034.002.patch, > SENTRY-2034.002.patch, SENTRY-2034.002.patch > > > Currently, there are no e2e tests that test the functionality of pulling the > notifications from HMS and processing them. Which include updating the update > the permissions based on the HMS updates. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-854) Refactor SentryGenericProviderBackend to use the client pool for creating client instance
[ https://issues.apache.org/jira/browse/SENTRY-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-854: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Refactor SentryGenericProviderBackend to use the client pool for creating > client instance > - > > Key: SENTRY-854 > URL: https://issues.apache.org/jira/browse/SENTRY-854 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: shenguoquan >Assignee: shenguoquan > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-941) Drop table should revert the ownership and permission rules to parent when directory is created within hive
[ https://issues.apache.org/jira/browse/SENTRY-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-941: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Drop table should revert the ownership and permission rules to parent when > directory is created within hive > --- > > Key: SENTRY-941 > URL: https://issues.apache.org/jira/browse/SENTRY-941 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: 2.1.0 > > > For example: if we have directory /tab1 owned by batchid:batchid and if we > create a partition through beeline /tabl/part1, when we drop this > table/partition part1 goes back to just hive:hive as that is the ground truth. > But seems like it might be useful if it can be batchid:batchid instead. This > came from one of the Sentry users, need to investigate further if this > behavior makes sense. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-2063) Add timestamp in Thrift API for HDFS integration
[ https://issues.apache.org/jira/browse/SENTRY-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2063: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Add timestamp in Thrift API for HDFS integration > > > Key: SENTRY-2063 > URL: https://issues.apache.org/jira/browse/SENTRY-2063 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.0.0 >Reporter: Na Li >Assignee: Na Li > Fix For: 2.1.0 > > > Add timestamp field in HDFS request to sentry and response from sentry. In > this way, sentry server can find when the HDFS client got update, and gets > all updates after that time. In this way, we can avoid missing any update -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-387) Thrift APIs seem to return "0" status code for some failed operations
[ https://issues.apache.org/jira/browse/SENTRY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-387: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Thrift APIs seem to return "0" status code for some failed operations > - > > Key: SENTRY-387 > URL: https://issues.apache.org/jira/browse/SENTRY-387 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > > For example, if serverName or action is null/empty, operation fails but we > still return 0 status code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1871) Improve performance of ACL lookups for the Sentry Name Node plugin
[ https://issues.apache.org/jira/browse/SENTRY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1871: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Improve performance of ACL lookups for the Sentry Name Node plugin > -- > > Key: SENTRY-1871 > URL: https://issues.apache.org/jira/browse/SENTRY-1871 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Affects Versions: 1.8.0 >Reporter: Brian Towles >Assignee: Brian Towles > Fix For: 2.1.0 > > > The performance of acl lookups for the HDFS is slow for very large numbers of > paths because the paths are stored as a tree on the NN plugin side. When a > lookup on an ACL occurs (getACLFeature call) it is a O(log n) operation for > each one. This can be changed to a Hash lookup based on path of only paths > with authorization objects attached to them. This would change it to a O(1) > lookup per path. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1129) Merge the methods related to grant/revoke privileges
[ https://issues.apache.org/jira/browse/SENTRY-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1129: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Merge the methods related to grant/revoke privileges > > > Key: SENTRY-1129 > URL: https://issues.apache.org/jira/browse/SENTRY-1129 > Project: Sentry > Issue Type: Bug >Affects Versions: 1.7.0 >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Fix For: 2.1.0 > > > 1. Merge the methods grantURIPrivilege, grantServerPrivilege ... to > grantPrivilegeToRole > 2. Merge the methods revokeURIPrivilege revokeServerPrivilege ... to > revokePrivilegeFromRole -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-292) Would be good to have some way to verify if the Sentry backend db is properly initialized
[ https://issues.apache.org/jira/browse/SENTRY-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-292: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Would be good to have some way to verify if the Sentry backend db is properly > initialized > - > > Key: SENTRY-292 > URL: https://issues.apache.org/jira/browse/SENTRY-292 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Labels: grant/revoke > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-524) [Unit Test] testMovingTable1 test fails sporadically while executing Hive query
[
https://issues.apache.org/jira/browse/SENTRY-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-524:
---
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> [Unit Test] testMovingTable1 test fails sporadically while executing Hive
> query
> ---
>
> Key: SENTRY-524
> URL: https://issues.apache.org/jira/browse/SENTRY-524
> Project: Sentry
> Issue Type: Test
>Affects Versions: 1.5.0
>Reporter: Lenni Kuff
>Priority: Blocker
> Fix For: 2.1.0
>
>
> https://builds.apache.org/job/Sentry-jdk-1.7/org.apache.sentry$sentry-tests-hive/99/testReport/junit/org.apache.sentry.tests.e2e.hive/TestMovingToProduction/testMovingTable1/
> The MR logs are not currently available (something we should fix), making
> this a bit tricky to debug.
> {code}
> Error Message
> Error while processing statement: FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask
> Stacktrace
> java.sql.SQLException: Error while processing statement: FAILED: Execution
> Error, return code 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:277)
> at
> org.apache.sentry.tests.e2e.hive.TestMovingToProduction.testMovingTable1(TestMovingToProduction.java:104)
> Standard Output
> 2014-11-13 18:21:46,307 (main) [INFO -
> org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.setupTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:197)]
> BaseDir = /tmp/1415902906306-0
> 2014-11-13 18:21:46,493 (main) [INFO -
> org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:375)]
> starting cluster: numNameNodes=1, numDataNodes=2
> 2014-11-13 18:21:48,024 (main) [WARN -
> org.apache.hadoop.util.NativeCodeLoader.(NativeCodeLoader.java:62)]
> Unable to l
> ...[truncated 1134025 bytes]...
> ) [INFO -
> org.apache.hadoop.fs.FileSystem.processDeleteOnExit(FileSystem.java:1388)]
> Ignoring failure to deleteOnExit for path
> hdfs://localhost:55195/data/db_2.db/tb_1/.hive-staging_hive_2014-11-13_18-22-07_668_4739504379041409322-3
> 2014-11-13 18:22:18,829 (Thread-34) [INFO -
> org.apache.hadoop.fs.FileSystem.processDeleteOnExit(FileSystem.java:1388)]
> Ignoring failure to deleteOnExit for path
> hdfs://localhost:55195/data/db_2.db/tb_1/.hive-staging_hive_2014-11-13_18-22-10_952_1973260947588109735-4
> {code}
> Marked as blocker since this is a unit test failure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-1502) Multiple tests in TestSentryStore are not testing useful things
[
https://issues.apache.org/jira/browse/SENTRY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kalyan kumar kalvagadda updated SENTRY-1502:
Fix Version/s: (was: 2.0.0)
2.1.0
Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the
fix version if you intend to make it into 2.0.0 release.
> Multiple tests in TestSentryStore are not testing useful things
> ---
>
> Key: SENTRY-1502
> URL: https://issues.apache.org/jira/browse/SENTRY-1502
> Project: Sentry
> Issue Type: Test
> Components: Sentry
>Affects Versions: 1.7.0, 2.0.0
>Reporter: Alexander Kolbasov
>Assignee: Ruiming Zhou
> Labels: patch
> Fix For: 2.1.0
>
> Attachments: SENTRY-1502.001.patch
>
>
> I noticed that multiple unit tests in TestSentryStore are not testing useful
> things. For example:
> {code}
> @Test
> public void testCreateDropRole() throws Exception {
> String roleName = "test-drop-role";
> long seqId = sentryStore.createSentryRole(roleName).getSequenceId();
> assertEquals(seqId + 1,
> sentryStore.dropSentryRole(roleName).getSequenceId());
> }
> {code}
> So this code only tests that there are no exceptions thrown. The assert is
> bogus - it tests that there was a single transaction in between which is a
> wrong test in the first place - number of transactions isn't a functionality.
> The test doesn't verify whether the role was actually created and whether it
> was correctly dropped. And it is similar for other tests as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENTRY-361) Sentry server should use sentry-site.xml in conf directory by default
[ https://issues.apache.org/jira/browse/SENTRY-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-361: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Sentry server should use sentry-site.xml in conf directory by default > - > > Key: SENTRY-361 > URL: https://issues.apache.org/jira/browse/SENTRY-361 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Dapeng Sun >Assignee: Dapeng Sun > Fix For: 2.1.0 > > Attachments: SENTRY-361.patch, SENTRY-361_002.patch, > SENTRY-361_003.patch, SENTRY-361_004.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 ] kalyan kumar kalvagadda updated SENTRY-1068: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > 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: 2.1.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.4.14#64029)
[jira] [Updated] (SENTRY-232) Refactor the solr e2e tests to run against both MiniCluster and itest clusters
[ https://issues.apache.org/jira/browse/SENTRY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-232: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Refactor the solr e2e tests to run against both MiniCluster and itest clusters > -- > > Key: SENTRY-232 > URL: https://issues.apache.org/jira/browse/SENTRY-232 > Project: Sentry > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Vamsee Yarlagadda >Assignee: Vamsee Yarlagadda > Fix For: 2.1.0 > > > Currently, the sentry e2e tests can only be run against a > MiniSolrCloudCluster. We need to refactor the code in such a way that we can > run the same tests against downstream itest clusters as well. This may > involve in writing new interfaces and functions to support both the > environments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-982) Test that all solr admin handlers are protected
[ https://issues.apache.org/jira/browse/SENTRY-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-982: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Test that all solr admin handlers are protected > --- > > Key: SENTRY-982 > URL: https://issues.apache.org/jira/browse/SENTRY-982 > Project: Sentry > Issue Type: Task > Components: Solr Plugin >Affects Versions: 1.7.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 2.1.0 > > > As of today we verify individual handlers but don't verify that all handlers > are protected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-440) Update jdo and object model to store grantorPrincipal in the mappings
[ https://issues.apache.org/jira/browse/SENTRY-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-440: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Update jdo and object model to store grantorPrincipal in the mappings > - > > Key: SENTRY-440 > URL: https://issues.apache.org/jira/browse/SENTRY-440 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-295) Revamp client configuration properties and add tests for deprecated properties
[ https://issues.apache.org/jira/browse/SENTRY-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-295: --- Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Revamp client configuration properties and add tests for deprecated properties > -- > > Key: SENTRY-295 > URL: https://issues.apache.org/jira/browse/SENTRY-295 > Project: Sentry > Issue Type: Test >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur > Labels: grant/revoke > Fix For: 2.1.0 > > > https://github.com/apache/incubator-sentry/blob/master/sentry-binding/sentry-binding-hive/src/main/java/org/apache/sentry/binding/hive/conf/HiveAuthzConf.java -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENTRY-1720) Re-enable or remove TestHDFSIntegrationWithHA
[ https://issues.apache.org/jira/browse/SENTRY-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1720: Fix Version/s: (was: 2.0.0) 2.1.0 Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the fix version if you intend to make it into 2.0.0 release. > Re-enable or remove TestHDFSIntegrationWithHA > -- > > Key: SENTRY-1720 > URL: https://issues.apache.org/jira/browse/SENTRY-1720 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov > Labels: test > Fix For: 2.1.0 > > > The TestHDFSIntegrationWithHA test is disabled now. We need to either fix it > or remove if it is no longer applicable. > The TestHDFSIntegration test is disabled as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
