[jira] [Updated] (SENTRY-367) Add end to end tests for audit log

[ https://issues.apache.org/jira/browse/SENTRY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Ma updated SENTRY-367: Attachment: sentry-367.v1.patch The patch for end to end tests is available. > Add end to end tests for au

[jira] [Commented] (SENTRY-339) Remove PrivilegeName column and constructPrivilegeName() function

[ https://issues.apache.org/jira/browse/SENTRY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074138#comment-14074138 ] SentryQA commented on SENTRY-339: - Here are the results of testing the latest attachment h

[jira] [Updated] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

[ https://issues.apache.org/jira/browse/SENTRY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-368: -- Description: 1.Removed unused {{requestorUserGroupNames}} in comments at line 208 and 240; 2.Removed un

[jira] [Updated] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

[ https://issues.apache.org/jira/browse/SENTRY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-368: -- Attachment: SENTRY-368_003.patch > Remove unused field in SentryPolicyServiceClient.java >

[jira] [Updated] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

[ https://issues.apache.org/jira/browse/SENTRY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-368: -- Attachment: (was: SENTRY-368.patch) > Remove unused field in SentryPolicyServiceClient.java > -

[jira] [Updated] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

[ https://issues.apache.org/jira/browse/SENTRY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-368: -- Attachment: SENTRY-368.patch A simple patch fixed. > Remove unused field in SentryPolicyServiceClient.

[jira] [Updated] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

[ https://issues.apache.org/jira/browse/SENTRY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated SENTRY-368: -- Attachment: SENTRY-368_002.patch > Remove unused field in SentryPolicyServiceClient.java >

[jira] [Created] (SENTRY-368) Remove unused field in SentryPolicyServiceClient.java

Dapeng Sun created SENTRY-368: - Summary: Remove unused field in SentryPolicyServiceClient.java Key: SENTRY-368 URL: https://issues.apache.org/jira/browse/SENTRY-368 Project: Sentry Issue Type: Bu

[jira] [Updated] (SENTRY-365) Create release branch for 1.4.0

[ https://issues.apache.org/jira/browse/SENTRY-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuong Truong updated SENTRY-365: Attachment: SENTRY-365.patch Patch to change all pom.xml to 1.4.0-incubating. > Create release bra

[jira] [Reopened] (SENTRY-333) Add conf directory to sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tuong Truong reopened SENTRY-333: - Looks like my patch was not applied as it. the commit was done w/o conf directory created. I just

[jira] [Created] (SENTRY-367) Add end to end tests for audit log

Colin Ma created SENTRY-367: --- Summary: Add end to end tests for audit log Key: SENTRY-367 URL: https://issues.apache.org/jira/browse/SENTRY-367 Project: Sentry Issue Type: Sub-task Repo

[jira] [Commented] (SENTRY-365) Create release branch for 1.4.0

[ https://issues.apache.org/jira/browse/SENTRY-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073950#comment-14073950 ] Tuong Truong commented on SENTRY-365: - Hi Srayvia, Our Jenkins handles the release an

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073936#comment-14073936 ] guoquanshen commented on SENTRY-362: hi [~gchanan] <--Why did SolrAuthzConf change fro

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073928#comment-14073928 ] Gregory Chanan commented on SENTRY-362: --- [~guoquan] I looked at the latest patch. L

[jira] [Commented] (SENTRY-364) Bump up hive and hadoop versions from SNAPSHOT to released bits

[ https://issues.apache.org/jira/browse/SENTRY-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073926#comment-14073926 ] Dapeng Sun commented on SENTRY-364: --- Hi [~sravya], Does the jira means change {noformat}

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073925#comment-14073925 ] guoquanshen commented on SENTRY-362: hi [~gchanan], thank your for your comments. yeah

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14073924#comment-14073924 ] Dapeng Sun commented on SENTRY-361: --- Thanks [~tctruong213]. I really appreciate your wor

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073920#comment-14073920 ] Gregory Chanan commented on SENTRY-362: --- bq. think if the sentry use the db store,

[jira] [Updated] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guoquanshen updated SENTRY-362: --- Attachment: SENTRY-362.patch > When sentry integrate into solr, the create instance of backend needs

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073910#comment-14073910 ] guoquanshen commented on SENTRY-362: hi [~gchanan], thanks your comments. <---Should w

[jira] [Created] (SENTRY-366) Update the versions on trunk after branching

Sravya Tirukkovalur created SENTRY-366: -- Summary: Update the versions on trunk after branching Key: SENTRY-366 URL: https://issues.apache.org/jira/browse/SENTRY-366 Project: Sentry Issue

[jira] [Created] (SENTRY-365) Create release branch for 1.4.0

Sravya Tirukkovalur created SENTRY-365: -- Summary: Create release branch for 1.4.0 Key: SENTRY-365 URL: https://issues.apache.org/jira/browse/SENTRY-365 Project: Sentry Issue Type: Sub-ta

[jira] [Updated] (SENTRY-364) Bump up hive and hadoop versions from SNAPSHOT to released bits

[ https://issues.apache.org/jira/browse/SENTRY-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur updated SENTRY-364: --- Issue Type: Sub-task (was: Task) Parent: SENTRY-356 > Bump up hive and hadoo

[jira] [Created] (SENTRY-364) Bump up hive and hadoop versions from SNAPSHOT to released bits

Sravya Tirukkovalur created SENTRY-364: -- Summary: Bump up hive and hadoop versions from SNAPSHOT to released bits Key: SENTRY-364 URL: https://issues.apache.org/jira/browse/SENTRY-364 Project: Se

[jira] [Commented] (SENTRY-339) Remove PrivilegeName column and constructPrivilegeName() function

[ https://issues.apache.org/jira/browse/SENTRY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073895#comment-14073895 ] Sravya Tirukkovalur commented on SENTRY-339: @Arun, looks like the pre commit

[jira] [Updated] (SENTRY-363) CTAS from view is requiring select on underlying table

[ https://issues.apache.org/jira/browse/SENTRY-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sravya Tirukkovalur updated SENTRY-363: --- Attachment: SENTRY-363.1.patch > CTAS from view is requiring select on underlying tab

[jira] [Created] (SENTRY-363) CTAS from view is requiring select on underlying table

Sravya Tirukkovalur created SENTRY-363: -- Summary: CTAS from view is requiring select on underlying table Key: SENTRY-363 URL: https://issues.apache.org/jira/browse/SENTRY-363 Project: Sentry

[jira] [Updated] (SENTRY-339) Remove PrivilegeName column and constructPrivilegeName() function

[ https://issues.apache.org/jira/browse/SENTRY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated SENTRY-339: --- Attachment: SENTRY-339.4.patch uploaded latest patch > Remove PrivilegeName column and constructPriv

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073522#comment-14073522 ] Gregory Chanan commented on SENTRY-362: --- [~guoquan] good idea! A couple of comments

[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 ] Tuong Truong updated SENTRY-361: Affects Version/s: 1.4.0 > Sentry server should use sentry-site.xml in conf directory by default >

[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 ] Tuong Truong updated SENTRY-361: Fix Version/s: 1.4.0 > Sentry server should use sentry-site.xml in conf directory by default >

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14073354#comment-14073354 ] Tuong Truong commented on SENTRY-361: - Thanks, Dapeng. This was on my list to complet

[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 ] Dapeng Sun updated SENTRY-361: -- Attachment: SENTRY-361_002.patch > Sentry server should use sentry-site.xml in conf directory by defaul

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072999#comment-14072999 ] guoquanshen commented on SENTRY-362: These errors seem to not relate my patch > When

[jira] [Commented] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072993#comment-14072993 ] SentryQA commented on SENTRY-362: - Here are the results of testing the latest attachment h

[jira] [Commented] (SENTRY-360) The configuration files like "sentry-site.xml" should be packaged into sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072984#comment-14072984 ] SentryQA commented on SENTRY-360: - Here are the results of testing the latest attachment h

[jira] [Updated] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guoquanshen updated SENTRY-362: --- Attachment: SENTRY-362.patch > When sentry integrate into solr, the create instance of backend needs

[jira] [Updated] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guoquanshen updated SENTRY-362: --- Description: whatever Sentry Solr plugin integration with db store or file store, the create instanc

[jira] [Updated] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guoquanshen updated SENTRY-362: --- Description: whatever Sentry Solr plugin integration with db store or file store, the create instanc

[jira] [Updated] (SENTRY-362) When sentry integrate into solr, the create instance of backend needs configure parameters from solrAuthzConf not hadoopConf

[ https://issues.apache.org/jira/browse/SENTRY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] guoquanshen updated SENTRY-362: --- Summary: When sentry integrate into solr, the create instance of backend needs configure parameters f

[jira] [Created] (SENTRY-362) When sentry solr plugin integration with DB store, the create instance of SimpleDBProviderBackend needs configure parameters from solrAuthzConf not hadoopConf

guoquanshen created SENTRY-362: -- Summary: When sentry solr plugin integration with DB store, the create instance of SimpleDBProviderBackend needs configure parameters from solrAuthzConf not hadoopConf Key: SENTRY-362