[jira] [Updated] (SENTRY-1317) Implement fencing required for active/passive
[ https://issues.apache.org/jira/browse/SENTRY-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated SENTRY-1317: - Attachment: SENTRY-1317.006-sentry-ha-redesign.patch Fix PMD error > Implement fencing required for active/passive > - > > Key: SENTRY-1317 > URL: https://issues.apache.org/jira/browse/SENTRY-1317 > Project: Sentry > Issue Type: Sub-task >Reporter: Sravya Tirukkovalur >Assignee: Colin Patrick McCabe > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1317.001-sentry-ha-redesign.patch, > SENTRY-1317.002-sentry-ha-redesign.patch, > SENTRY-1317.003-sentry-ha-redesign.patch, > SENTRY-1317.004-sentry-ha-redesign.patch, > SENTRY-1317.005-sentry-ha-redesign.patch, > SENTRY-1317.006-sentry-ha-redesign.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1317) Implement fencing required for active/passive
[
https://issues.apache.org/jira/browse/SENTRY-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366623#comment-15366623
]
Hadoop QA commented on SENTRY-1317:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816679/SENTRY-1317.006-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to 25 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.dbprovider.TestDbPrivilegesAtFunctionScope
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.ha.TestHaEnd2End
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.ha.TestHaEnd2End
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithoutSecurity
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestAuthorizingDDLAuditLogWithKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceForPoolWithKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.service.thrift.TestSentryGenericServiceIntegration
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceImportExport
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.tools.TestSentryShellHive
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceWithInvalidMsgSize
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.tools.TestSentryShellSolr
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.service.thrift.TestAuditLogForSentryGenericService
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServerForPoolWithoutKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceIntegration
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceClientPool
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.tools.TestSentryConfigToolSolr
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServerWithoutKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceWithKerberos
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceMetrics
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.thrift.TestSentryServiceFailureCase
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.tools.TestSentryShellKafka
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestLeaderStatus
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1836/console
This message is automatically generated.
> Implement fencing required for active/passive
> -
>
> Key: SENTRY-1317
> URL: https://issues.apache.org/jira/browse/SENTRY-1317
> Project: Sentry
> Issue Type: Sub-task
>Reporter: Sravya Tirukkovalur
>Assignee: Colin Patrick McCabe
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1317.001-sentry-ha-redesign.patch,
> SENTRY-1317.002-sentry-ha-redesign.patch,
> SENTRY-1317.003-sentry-ha-redesign.patch,
> SENTRY-1317.004-sentry-ha-redesign.patch,
> SENTRY-1317.005-sentry-ha-redesign.patch,
> SENTRY-1317.006-sentry-ha-redesign.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SENTRY-1366) Test Alter table rename when there are no partitions
[ https://issues.apache.org/jira/browse/SENTRY-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365711#comment-15365711 ] Ke Jia commented on SENTRY-1366: Hi [~sravya] and [~dapengsun], I uploaded the patch and create the RB,. Could you help me review. > Test Alter table rename when there are no partitions > > > Key: SENTRY-1366 > URL: https://issues.apache.org/jira/browse/SENTRY-1366 > Project: Sentry > Issue Type: Test >Reporter: Sravya Tirukkovalur >Assignee: Ke Jia > Attachments: SENTRY-1366-001.patch, SENTRY-1366-001.patch, > SENTRY-1366-002.patch, SENTRY-1366-002.patch, SENTRY-1366-003.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-898) [column level privilege] with column level privilege, show partitions fails, SemanticException No valid privileges
[
https://issues.apache.org/jira/browse/SENTRY-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ke Jia updated SENTRY-898:
--
Attachment: SENTRY-898-001.patch
> [column level privilege] with column level privilege, show partitions fails,
> SemanticException No valid privileges
> --
>
> Key: SENTRY-898
> URL: https://issues.apache.org/jira/browse/SENTRY-898
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 1.5.1
>Reporter: Anne Yu
>Assignee: Hao Hao
> Attachments: SENTRY-898-001.patch
>
>
> If grant column level privilege to test user on a partition, show partitions
> fails to list the permitted partition with Error: Error while compiling
> statement: FAILED: SemanticException No valid privileges;
> {code}
> CREATE TABLE pageviews (userid VARCHAR(64), link STRING, came_from STRING)
> PARTITIONED BY (datestamp STRING, counter INT) CLUSTERED BY (userid) INTO 256
> BUCKETS STORED AS ORC;
> grant select(datestamp) on table pageviews to role test_par;
> grant role test_par to group test_user;
> show partitions pageviews;
> {code}
> cc [~guoquan], [~sravya], [~lskuff]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SENTRY-898) [column level privilege] with column level privilege, show partitions fails, SemanticException No valid privileges
[
https://issues.apache.org/jira/browse/SENTRY-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ke Jia updated SENTRY-898:
--
Status: Patch Available (was: Open)
> [column level privilege] with column level privilege, show partitions fails,
> SemanticException No valid privileges
> --
>
> Key: SENTRY-898
> URL: https://issues.apache.org/jira/browse/SENTRY-898
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 1.5.1
>Reporter: Anne Yu
>Assignee: Hao Hao
>
> If grant column level privilege to test user on a partition, show partitions
> fails to list the permitted partition with Error: Error while compiling
> statement: FAILED: SemanticException No valid privileges;
> {code}
> CREATE TABLE pageviews (userid VARCHAR(64), link STRING, came_from STRING)
> PARTITIONED BY (datestamp STRING, counter INT) CLUSTERED BY (userid) INTO 256
> BUCKETS STORED AS ORC;
> grant select(datestamp) on table pageviews to role test_par;
> grant role test_par to group test_user;
> show partitions pageviews;
> {code}
> cc [~guoquan], [~sravya], [~lskuff]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SENTRY-898) [column level privilege] with column level privilege, show partitions fails, SemanticException No valid privileges
[
https://issues.apache.org/jira/browse/SENTRY-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365841#comment-15365841
]
Hadoop QA commented on SENTRY-898:
--
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816583/SENTRY-898-001.patch
against master.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.hive.TestMetadataObjectRetrieval
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.dbprovider.TestDbMetadataObjectRetrieval
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1835/console
This message is automatically generated.
> [column level privilege] with column level privilege, show partitions fails,
> SemanticException No valid privileges
> --
>
> Key: SENTRY-898
> URL: https://issues.apache.org/jira/browse/SENTRY-898
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 1.5.1
>Reporter: Anne Yu
>Assignee: Hao Hao
> Attachments: SENTRY-898-001.patch
>
>
> If grant column level privilege to test user on a partition, show partitions
> fails to list the permitted partition with Error: Error while compiling
> statement: FAILED: SemanticException No valid privileges;
> {code}
> CREATE TABLE pageviews (userid VARCHAR(64), link STRING, came_from STRING)
> PARTITIONED BY (datestamp STRING, counter INT) CLUSTERED BY (userid) INTO 256
> BUCKETS STORED AS ORC;
> grant select(datestamp) on table pageviews to role test_par;
> grant role test_par to group test_user;
> show partitions pageviews;
> {code}
> cc [~guoquan], [~sravya], [~lskuff]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SENTRY-1329) Adapt SentryMetaStorePostEventListener to write HMS notification logs
[ https://issues.apache.org/jira/browse/SENTRY-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur updated SENTRY-1329: Attachment: SENTRY-1329.2-sentry-ha-redesign.patch > Adapt SentryMetaStorePostEventListener to write HMS notification logs > - > > Key: SENTRY-1329 > URL: https://issues.apache.org/jira/browse/SENTRY-1329 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1329.0.patch, > SENTRY-1329.1-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-ha-redesign.patch, SENTRY-1329.2-sentry-hs-redesign.patch > > > After some preliminary testing of HMS NotificationLog in Sentry > (SENTRY-1324), we see that NotificationLog does not capture some information > today. See this [comment| > https://issues.apache.org/jira/browse/SENTRY-1324?focusedCommentId=15330859=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15330859] > for more information. > So with respect to capturing this information, the minimally invasive > approach is to just implement a custom MessageFactory > (hcatalog.message.factory.impl.json), which takes care of the serialization > and deseriazation of the message. We can just add additional information > without causing disruption to other clients. > As I was implementing this, I encountered the problem that there is a small > bug(in Hive trunk) which makes the MessageFactory not truly pluggable > (HIVE-14011 - Attached a fix). But it would be a while before Hive can make a > release with this fix and Sentry can move to this fixed version. > So in the interim, we can implement the Listener in Sentry and use custom > MessageFactory as well. I have done some testing on my side to make sure it > does not break other clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1317) Implement fencing required for active/passive
[ https://issues.apache.org/jira/browse/SENTRY-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated SENTRY-1317: - Attachment: SENTRY-1317.007-sentry-ha-redesign.patch Fix some issues where we were failing to create classes using reflection. > Implement fencing required for active/passive > - > > Key: SENTRY-1317 > URL: https://issues.apache.org/jira/browse/SENTRY-1317 > Project: Sentry > Issue Type: Sub-task >Reporter: Sravya Tirukkovalur >Assignee: Colin Patrick McCabe > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1317.001-sentry-ha-redesign.patch, > SENTRY-1317.002-sentry-ha-redesign.patch, > SENTRY-1317.003-sentry-ha-redesign.patch, > SENTRY-1317.004-sentry-ha-redesign.patch, > SENTRY-1317.005-sentry-ha-redesign.patch, > SENTRY-1317.006-sentry-ha-redesign.patch, > SENTRY-1317.007-sentry-ha-redesign.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1329) Adapt SentryMetaStorePostEventListener to write HMS notification logs
[
https://issues.apache.org/jira/browse/SENTRY-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366761#comment-15366761
]
Hadoop QA commented on SENTRY-1329:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816699/SENTRY-1329.2-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1837/console
This message is automatically generated.
> Adapt SentryMetaStorePostEventListener to write HMS notification logs
> -
>
> Key: SENTRY-1329
> URL: https://issues.apache.org/jira/browse/SENTRY-1329
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Reporter: Sravya Tirukkovalur
>Assignee: Sravya Tirukkovalur
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1329.0.patch,
> SENTRY-1329.1-sentry-ha-redesign.patch,
> SENTRY-1329.2-sentry-ha-redesign.patch,
> SENTRY-1329.2-sentry-ha-redesign.patch, SENTRY-1329.2-sentry-hs-redesign.patch
>
>
> After some preliminary testing of HMS NotificationLog in Sentry
> (SENTRY-1324), we see that NotificationLog does not capture some information
> today. See this [comment|
> https://issues.apache.org/jira/browse/SENTRY-1324?focusedCommentId=15330859=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15330859]
> for more information.
> So with respect to capturing this information, the minimally invasive
> approach is to just implement a custom MessageFactory
> (hcatalog.message.factory.impl.json), which takes care of the serialization
> and deseriazation of the message. We can just add additional information
> without causing disruption to other clients.
> As I was implementing this, I encountered the problem that there is a small
> bug(in Hive trunk) which makes the MessageFactory not truly pluggable
> (HIVE-14011 - Attached a fix). But it would be a while before Hive can make a
> release with this fix and Sentry can move to this fixed version.
> So in the interim, we can implement the Listener in Sentry and use custom
> MessageFactory as well. I have done some testing on my side to make sure it
> does not break other clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SENTRY-1329) Adapt SentryMetaStorePostEventListener to write HMS notification logs
[ https://issues.apache.org/jira/browse/SENTRY-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur updated SENTRY-1329: Attachment: SENTRY-1329.2-sentry-ha-redesign.patch > Adapt SentryMetaStorePostEventListener to write HMS notification logs > - > > Key: SENTRY-1329 > URL: https://issues.apache.org/jira/browse/SENTRY-1329 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1329.0.patch, > SENTRY-1329.1-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-ha-redesign.patch, SENTRY-1329.2-sentry-hs-redesign.patch > > > After some preliminary testing of HMS NotificationLog in Sentry > (SENTRY-1324), we see that NotificationLog does not capture some information > today. See this [comment| > https://issues.apache.org/jira/browse/SENTRY-1324?focusedCommentId=15330859=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15330859] > for more information. > So with respect to capturing this information, the minimally invasive > approach is to just implement a custom MessageFactory > (hcatalog.message.factory.impl.json), which takes care of the serialization > and deseriazation of the message. We can just add additional information > without causing disruption to other clients. > As I was implementing this, I encountered the problem that there is a small > bug(in Hive trunk) which makes the MessageFactory not truly pluggable > (HIVE-14011 - Attached a fix). But it would be a while before Hive can make a > release with this fix and Sentry can move to this fixed version. > So in the interim, we can implement the Listener in Sentry and use custom > MessageFactory as well. I have done some testing on my side to make sure it > does not break other clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1329) Adapt SentryMetaStorePostEventListener to write HMS notification logs
[
https://issues.apache.org/jira/browse/SENTRY-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366918#comment-15366918
]
Hadoop QA commented on SENTRY-1329:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816712/SENTRY-1329.3-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1841/console
This message is automatically generated.
> Adapt SentryMetaStorePostEventListener to write HMS notification logs
> -
>
> Key: SENTRY-1329
> URL: https://issues.apache.org/jira/browse/SENTRY-1329
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Reporter: Sravya Tirukkovalur
>Assignee: Sravya Tirukkovalur
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1329.0.patch,
> SENTRY-1329.1-sentry-ha-redesign.patch,
> SENTRY-1329.2-sentry-ha-redesign.patch,
> SENTRY-1329.2-sentry-ha-redesign.patch,
> SENTRY-1329.2-sentry-hs-redesign.patch, SENTRY-1329.3-sentry-ha-redesign.patch
>
>
> After some preliminary testing of HMS NotificationLog in Sentry
> (SENTRY-1324), we see that NotificationLog does not capture some information
> today. See this [comment|
> https://issues.apache.org/jira/browse/SENTRY-1324?focusedCommentId=15330859=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15330859]
> for more information.
> So with respect to capturing this information, the minimally invasive
> approach is to just implement a custom MessageFactory
> (hcatalog.message.factory.impl.json), which takes care of the serialization
> and deseriazation of the message. We can just add additional information
> without causing disruption to other clients.
> As I was implementing this, I encountered the problem that there is a small
> bug(in Hive trunk) which makes the MessageFactory not truly pluggable
> (HIVE-14011 - Attached a fix). But it would be a while before Hive can make a
> release with this fix and Sentry can move to this fixed version.
> So in the interim, we can implement the Listener in Sentry and use custom
> MessageFactory as well. I have done some testing on my side to make sure it
> does not break other clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SENTRY-709) Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
[ https://issues.apache.org/jira/browse/SENTRY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe reassigned SENTRY-709: --- Assignee: Colin Patrick McCabe (was: Sravya Tirukkovalur) > Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider > > > Key: SENTRY-709 > URL: https://issues.apache.org/jira/browse/SENTRY-709 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Reporter: Arun Suresh >Assignee: Colin Patrick McCabe >Priority: Critical > Labels: integration, roadmap > Attachments: SENTRY-709.1.patch, SENTRY-709.2.patch, > SENTRY-709.2.patch > > > Sentry HDFS namenode plugin uses a pre-committed version of the HDFS > AuthorizationProvider interface. HADOOP 2.7.0 will ship with the new > INodeAttributesProvider interface. > The Namenode plugin has to be refactored to use this new interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SENTRY-1318) Persist HMS DDL changes to NotificationLog and use HMS API to get recent notifications
[ https://issues.apache.org/jira/browse/SENTRY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur resolved SENTRY-1318. - > Persist HMS DDL changes to NotificationLog and use HMS API to get recent > notifications > -- > > Key: SENTRY-1318 > URL: https://issues.apache.org/jira/browse/SENTRY-1318 > Project: Sentry > Issue Type: Sub-task >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Description: Enabling usability of URI privileges for HMS write protection, such that URI with no scheme or authority can be handled. e.g GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' was: Enabling for HMS write protection, such that URI with no scheme or authority can be handled GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Description: Enabling usability of URI privileges for HMS write protection, such that URI with no scheme or authority can be handled. e.g GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' was: Enabling usability of URI privileges for HMS write protection, such that URI with no scheme or authority can be handled. e.g GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
Hao Hao created SENTRY-1390: --- Summary: Enabling usability of URI privileges for HMS binding Key: SENTRY-1390 URL: https://issues.apache.org/jira/browse/SENTRY-1390 Project: Sentry Issue Type: Task Reporter: Hao Hao Assignee: Hao Hao -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Description: Enabling for HMS write protection, such that URI with no scheme or authority can be handled GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > > Enabling for HMS write protection, such that URI with no scheme or authority > can be handled GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1329) Adapt SentryMetaStorePostEventListener to write HMS notification logs
[ https://issues.apache.org/jira/browse/SENTRY-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur updated SENTRY-1329: Attachment: SENTRY-1329.3-sentry-ha-redesign.patch > Adapt SentryMetaStorePostEventListener to write HMS notification logs > - > > Key: SENTRY-1329 > URL: https://issues.apache.org/jira/browse/SENTRY-1329 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1329.0.patch, > SENTRY-1329.1-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-ha-redesign.patch, > SENTRY-1329.2-sentry-hs-redesign.patch, SENTRY-1329.3-sentry-ha-redesign.patch > > > After some preliminary testing of HMS NotificationLog in Sentry > (SENTRY-1324), we see that NotificationLog does not capture some information > today. See this [comment| > https://issues.apache.org/jira/browse/SENTRY-1324?focusedCommentId=15330859=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15330859] > for more information. > So with respect to capturing this information, the minimally invasive > approach is to just implement a custom MessageFactory > (hcatalog.message.factory.impl.json), which takes care of the serialization > and deseriazation of the message. We can just add additional information > without causing disruption to other clients. > As I was implementing this, I encountered the problem that there is a small > bug(in Hive trunk) which makes the MessageFactory not truly pluggable > (HIVE-14011 - Attached a fix). But it would be a while before Hive can make a > release with this fix and Sentry can move to this fixed version. > So in the interim, we can implement the Listener in Sentry and use custom > MessageFactory as well. I have done some testing on my side to make sure it > does not break other clients. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-709) Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
[
https://issues.apache.org/jira/browse/SENTRY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366939#comment-15366939
]
Hadoop QA commented on SENTRY-709:
--
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816720/SENTRY-709.003-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1842/console
This message is automatically generated.
> Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
>
>
> Key: SENTRY-709
> URL: https://issues.apache.org/jira/browse/SENTRY-709
> Project: Sentry
> Issue Type: Improvement
> Components: Hdfs Plugin
>Reporter: Arun Suresh
>Assignee: Colin Patrick McCabe
>Priority: Critical
> Labels: integration, roadmap
> Attachments: SENTRY-709.003-sentry-ha-redesign.patch,
> SENTRY-709.1.patch, SENTRY-709.2.patch, SENTRY-709.2.patch
>
>
> Sentry HDFS namenode plugin uses a pre-committed version of the HDFS
> AuthorizationProvider interface. HADOOP 2.7.0 will ship with the new
> INodeAttributesProvider interface.
> The Namenode plugin has to be refactored to use this new interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SENTRY-1389) Handle updating HMSState for HDFS plugin in HMSFollower
Sravya Tirukkovalur created SENTRY-1389: --- Summary: Handle updating HMSState for HDFS plugin in HMSFollower Key: SENTRY-1389 URL: https://issues.apache.org/jira/browse/SENTRY-1389 Project: Sentry Issue Type: Sub-task Reporter: Sravya Tirukkovalur -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Description: Enabling usability of URI privileges for HMS write protection, such that URI with no scheme or authority can be handled. e.g * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' was: Enabling usability of URI privileges for HMS write protection, such that URI with no scheme or authority can be handled. e.g GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SENTRY-1279) Support of URI privilege without scheme should be configurable
[ https://issues.apache.org/jira/browse/SENTRY-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved SENTRY-1279. - Resolution: Won't Fix > Support of URI privilege without scheme should be configurable > --- > > Key: SENTRY-1279 > URL: https://issues.apache.org/jira/browse/SENTRY-1279 > Project: Sentry > Issue Type: Sub-task >Reporter: Hao Hao > > If the underlying storage is a mix usage of s3, hdfs, then defaultFS property > should not be used for relaxing the check of URI privilege without scheme. We > should make it configurable for cluster admin to decide whether to rely on > defaultFS property based on the underlying storage setting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1391) Add more test cases for perm and temp UDF
[ https://issues.apache.org/jira/browse/SENTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1391: Attachment: SENTRY-1391.0.patch > Add more test cases for perm and temp UDF > - > > Key: SENTRY-1391 > URL: https://issues.apache.org/jira/browse/SENTRY-1391 > Project: Sentry > Issue Type: Test > Components: UDF >Reporter: Hao Hao > Attachments: SENTRY-1391.0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1391) Add more test cases for perm and temp UDF
[ https://issues.apache.org/jira/browse/SENTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1391: Assignee: Hao Hao Status: Patch Available (was: Open) > Add more test cases for perm and temp UDF > - > > Key: SENTRY-1391 > URL: https://issues.apache.org/jira/browse/SENTRY-1391 > Project: Sentry > Issue Type: Test > Components: UDF >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1391.0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-709) Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
[
https://issues.apache.org/jira/browse/SENTRY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366928#comment-15366928
]
Colin Patrick McCabe commented on SENTRY-709:
-
[~sravya], do you mind if I pick this one up?
Looks like the {{INodeAttributeProvider}} class exists in the Hadoop 2.7.2
release, so I'm going to try rebasing on that.
> Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
>
>
> Key: SENTRY-709
> URL: https://issues.apache.org/jira/browse/SENTRY-709
> Project: Sentry
> Issue Type: Improvement
> Components: Hdfs Plugin
>Reporter: Arun Suresh
>Assignee: Colin Patrick McCabe
>Priority: Critical
> Labels: integration, roadmap
> Attachments: SENTRY-709.1.patch, SENTRY-709.2.patch,
> SENTRY-709.2.patch
>
>
> Sentry HDFS namenode plugin uses a pre-committed version of the HDFS
> AuthorizationProvider interface. HADOOP 2.7.0 will ship with the new
> INodeAttributesProvider interface.
> The Namenode plugin has to be refactored to use this new interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Deleted] (SENTRY-1318) Persist HMS DDL changes to NotificationLog and use HMS API to get recent notifications
[ https://issues.apache.org/jira/browse/SENTRY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur deleted SENTRY-1318: > Persist HMS DDL changes to NotificationLog and use HMS API to get recent > notifications > -- > > Key: SENTRY-1318 > URL: https://issues.apache.org/jira/browse/SENTRY-1318 > Project: Sentry > Issue Type: Sub-task >Reporter: Sravya Tirukkovalur >Assignee: Sravya Tirukkovalur > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-709) Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
[ https://issues.apache.org/jira/browse/SENTRY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated SENTRY-709: Attachment: SENTRY-709.003-sentry-ha-redesign.patch > Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider > > > Key: SENTRY-709 > URL: https://issues.apache.org/jira/browse/SENTRY-709 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Reporter: Arun Suresh >Assignee: Colin Patrick McCabe >Priority: Critical > Labels: integration, roadmap > Attachments: SENTRY-709.003-sentry-ha-redesign.patch, > SENTRY-709.1.patch, SENTRY-709.2.patch, SENTRY-709.2.patch > > > Sentry HDFS namenode plugin uses a pre-committed version of the HDFS > AuthorizationProvider interface. HADOOP 2.7.0 will ship with the new > INodeAttributesProvider interface. > The Namenode plugin has to be refactored to use this new interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-709) Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider
[ https://issues.apache.org/jira/browse/SENTRY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated SENTRY-709: Status: Patch Available (was: Open) > Refactor Sentry HDFS Namenode Plugin to use HDFS INodeAttributesProvider > > > Key: SENTRY-709 > URL: https://issues.apache.org/jira/browse/SENTRY-709 > Project: Sentry > Issue Type: Improvement > Components: Hdfs Plugin >Reporter: Arun Suresh >Assignee: Colin Patrick McCabe >Priority: Critical > Labels: integration, roadmap > Attachments: SENTRY-709.003-sentry-ha-redesign.patch, > SENTRY-709.1.patch, SENTRY-709.2.patch, SENTRY-709.2.patch > > > Sentry HDFS namenode plugin uses a pre-committed version of the HDFS > AuthorizationProvider interface. HADOOP 2.7.0 will ship with the new > INodeAttributesProvider interface. > The Namenode plugin has to be refactored to use this new interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Attachment: SENTRY-1390.0.patch > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1390.0.patch > > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Affects Version/s: 1.8.0 > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Affects Versions: 1.8.0 >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1390.0.patch > > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Status: Patch Available (was: Open) > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1390.0.patch > > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[
https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366985#comment-15366985
]
Hadoop QA commented on SENTRY-1390:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816725/SENTRY-1390.0.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1843/console
This message is automatically generated.
> Enabling usability of URI privileges for HMS binding
>
>
> Key: SENTRY-1390
> URL: https://issues.apache.org/jira/browse/SENTRY-1390
> Project: Sentry
> Issue Type: Task
> Components: URI
>Affects Versions: 1.8.0
>Reporter: Hao Hao
>Assignee: Hao Hao
> Attachments: SENTRY-1390.0.patch
>
>
> Enabling usability of URI privileges for HMS write protection, such that URI
> with no scheme or authority can be handled. e.g
> * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table'
> * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SENTRY-1390) Enabling usability of URI privileges for HMS binding
[ https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1390: Component/s: URI > Enabling usability of URI privileges for HMS binding > > > Key: SENTRY-1390 > URL: https://issues.apache.org/jira/browse/SENTRY-1390 > Project: Sentry > Issue Type: Task > Components: URI >Affects Versions: 1.8.0 >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1390.0.patch > > > Enabling usability of URI privileges for HMS write protection, such that URI > with no scheme or authority can be handled. e.g > * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1175) Improve usability of URI privileges when granting URIs
[ https://issues.apache.org/jira/browse/SENTRY-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1175: Component/s: (was: Sentry) URI > Improve usability of URI privileges when granting URIs > -- > > Key: SENTRY-1175 > URL: https://issues.apache.org/jira/browse/SENTRY-1175 > Project: Sentry > Issue Type: Sub-task > Components: URI >Affects Versions: 1.6.0 >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: 1.8.0 > > Attachments: SENTRY-1175.0.patch > > > If URI has no scheme and authority when granting URI privileges, e.g GRANT > ALL ON URI '/path/to/table'. Sentry should automatically handle it with > default scheme and authority based on the Hadoop configs Sentry has been > given. > There are two places could be changed to support it: > * When grant the URI privileges > * When check the URI privileges > However, when granting the URI privileges, the URI path does not necessary > needs to be presented in the filesystem, thus choose to make the URI fully > qualified during the privileges checking time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1001) Improve usability of URIs and URI privileges
[ https://issues.apache.org/jira/browse/SENTRY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1001: Component/s: URI > Improve usability of URIs and URI privileges > - > > Key: SENTRY-1001 > URL: https://issues.apache.org/jira/browse/SENTRY-1001 > Project: Sentry > Issue Type: Bug > Components: URI >Affects Versions: 1.6.0 >Reporter: Lenni Kuff >Assignee: Hao Hao > Fix For: 1.8.0 > > > Sentry currently requires users to have their URI privileges exactly match > what is in the CREATE TABLE statement. For example, the following will not > work: > GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table' > CREATE EXTERNAL TABLE foo LOCATION '/path/to/table' > To make this more usable, Sentry should automatically handle this case and > apply whatever the default scheme and authority based on the HDFS configs > Sentry has been given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1391) Add more test cases for perm and temp UDF
[ https://issues.apache.org/jira/browse/SENTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1391: Component/s: UDF > Add more test cases for perm and temp UDF > - > > Key: SENTRY-1391 > URL: https://issues.apache.org/jira/browse/SENTRY-1391 > Project: Sentry > Issue Type: Test > Components: UDF >Reporter: Hao Hao > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1391) Add more test cases for perm and temp UDF
[ https://issues.apache.org/jira/browse/SENTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1391: Description: Add more test cases for checking required permission for create/drop/execute perm/temp Hive UDF. > Add more test cases for perm and temp UDF > - > > Key: SENTRY-1391 > URL: https://issues.apache.org/jira/browse/SENTRY-1391 > Project: Sentry > Issue Type: Test > Components: UDF >Reporter: Hao Hao >Assignee: Hao Hao > Attachments: SENTRY-1391.0.patch > > > Add more test cases for checking required permission for create/drop/execute > perm/temp Hive UDF. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1391) Add more test cases for perm and temp UDF
[
https://issues.apache.org/jira/browse/SENTRY-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15367024#comment-15367024
]
Hadoop QA commented on SENTRY-1391:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12816728/SENTRY-1391.0.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/1844/console
This message is automatically generated.
> Add more test cases for perm and temp UDF
> -
>
> Key: SENTRY-1391
> URL: https://issues.apache.org/jira/browse/SENTRY-1391
> Project: Sentry
> Issue Type: Test
> Components: UDF
>Reporter: Hao Hao
>Assignee: Hao Hao
> Attachments: SENTRY-1391.0.patch
>
>
> Add more test cases for checking required permission for create/drop/execute
> perm/temp Hive UDF.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SENTRY-1295) Investigate malformed paths in HMS db
[
https://issues.apache.org/jira/browse/SENTRY-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Ma reassigned SENTRY-1295:
Assignee: Colin Ma
> Investigate malformed paths in HMS db
> -
>
> Key: SENTRY-1295
> URL: https://issues.apache.org/jira/browse/SENTRY-1295
> Project: Sentry
> Issue Type: Bug
>Reporter: Sravya Tirukkovalur
>Assignee: Colin Ma
>Priority: Critical
>
> Paths in HMS are expected to be in one of these forms:
> * hdfs://hostname:port/path
> * hdfs:///path
> * /path, in which case, scheme will be constructed from
> FileSystem.getDefaultURI
> * URIs with non hdfs scheme will just be ignored
> I came across atleast 2 sentry users where HMS did have paths which do not
> comply with above rules and hence HMS plugin initialization for pathupdates
> failed. See sentry-1260 and sentry-1270 for details on how these errors
> surface.
> With 1260 and 1270 we should have more information on what these malformed
> paths were. But we should continue to investigate and fix the root cause, It
> would most likely be in HMS code base. Until then, here is how you can
> diagnose and fix it manually:
> *Look for malformed paths in HMS* : Look in DBS as well as SDS tables.
> {code}
> SELECT "NAME", "DB_LOCATION_URI" FROM "DBS" WHERE NOT "DB_LOCATION_URI" LIKE
> 'hdfs://%/%';
> NAME | DB_LOCATION_URI
> ---+
> db_name | hdfs://nameservice1
> (1 row)
> {code}
> *Fix it manually updating the HMS location*
> {code}
> UPDATE DBS
> SET DB_LOCATION_URI='hdfs://nameservice1/user/hive/warehouse/db_name.db'
> WHERE DB_ID=12345;
> {code}
> Lets track occurrences of these malformed paths here:
> * hdfs://nameservice1 : Not sure why would any one create a db/table in root
> directory? Should we accept this in Sentry?
> What does SKEWED_COL_VALUE_LOC_MAP.location in HMS correspond to? Double
> check if there are any malformed paths here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
