[jira] [Created] (SENTRY-1775) Unit test for HMSFollower is not testing anything useful

Alexander Kolbasov created SENTRY-1775: -- Summary: Unit test for HMSFollower is not testing anything useful Key: SENTRY-1775 URL: https://issues.apache.org/jira/browse/SENTRY-1775 Project: Sentry

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Status: Patch Available (was: Open) > Permissions created before table creation are

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Attachment: SENTRY-1772.001-sentry-ha-redesign.patch > Permissions created before

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Status: Open (was: Patch Available) > Permissions created before table creation are

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Attachment: (was: SENTRY-1772.001-sentry-ha-redesign.patch) > Permissions

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016893#comment-16016893 ] Alexander Kolbasov commented on SENTRY-1772: Also need to fix unit test because it checks for

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016894#comment-16016894 ] Alexander Kolbasov commented on SENTRY-1772: A I side effect I discovered that the test is

[jira] [Updated] (SENTRY-1705) Do not start HMSFollower if Hive isn't configured

[ https://issues.apache.org/jira/browse/SENTRY-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1705: -- Attachment: SENTRY-1705.006-sentry-ha-redesign.patch v6. Remove extra check for metastore URI in HMSFollower.

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016826#comment-16016826 ] Hadoop QA commented on SENTRY-1736: --- Here are the results of testing the latest attachment

[jira] [Updated] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsee Yarlagadda updated SENTRY-1736: -- Resolution: Fixed Fix Version/s: sentry-ha-redesign Status: Resolved

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016792#comment-16016792 ] Vamsee Yarlagadda commented on SENTRY-1772: --- The change LGTM. Ship It! > Permissions created

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016787#comment-16016787 ] Hadoop QA commented on SENTRY-1736: --- Here are the results of testing the latest attachment

[jira] [Commented] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016781#comment-16016781 ] Alexander Kolbasov commented on SENTRY-1630: [~kkalyan] has a way to reproduce it in unit

[jira] [Assigned] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reassigned SENTRY-1630: -- Assignee: Sergio Peña (was: Lei (Eddy) Xu) > out of sequence error in

[jira] [Updated] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1630: --- Priority: Blocker (was: Critical) > out of sequence error in HMSFollower >

[jira] [Updated] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1736: Attachment: SENTRY-1736.005-sentry-ha-redesign.patch > Generic service

[jira] [Updated] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1736: Attachment: SENTRY-1736.004-sentry-ha-redesign.patch > Generic service

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016677#comment-16016677 ] Hadoop QA commented on SENTRY-1736: --- Here are the results of testing the latest attachment

[jira] [Assigned] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reassigned SENTRY-1774: -- Assignee: Sergio Peña > HMSFollower should always depend on persisted

[jira] [Commented] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016630#comment-16016630 ] kalyan kumar kalvagadda commented on SENTRY-1774: - [~akolb] SENTRY-1760 just talks about

[jira] [Commented] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016620#comment-16016620 ] Alexander Kolbasov commented on SENTRY-1774: How is this different from SENTRY-1760? >

[jira] [Updated] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1774: --- Priority: Blocker (was: Major) > HMSFollower should always depend on persisted

[jira] [Updated] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

[ https://issues.apache.org/jira/browse/SENTRY-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1774: --- Affects Version/s: (was: 1.8.0) sentry-ha-redesign >

[jira] [Created] (SENTRY-1774) HMSFollower should always depend on persisted information to decide is full snapshot is needed

kalyan kumar kalvagadda created SENTRY-1774: --- Summary: HMSFollower should always depend on persisted information to decide is full snapshot is needed Key: SENTRY-1774 URL:

[jira] [Updated] (SENTRY-1770) Avoid more detaches on commit

[ https://issues.apache.org/jira/browse/SENTRY-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1770: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Avoid more

[jira] [Updated] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1736: Attachment: SENTRY-1736.004-sentry-ha-redesign.patch > Generic service

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016476#comment-16016476 ] Hadoop QA commented on SENTRY-1736: --- Here are the results of testing the latest attachment

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016453#comment-16016453 ] kalyan kumar kalvagadda commented on SENTRY-1736: - After a discussion with the [~akolb]

[jira] [Commented] (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:comment-tabpanel=16016449#comment-16016449 ] Hadoop QA commented on SENTRY-1761: --- Here are the results of testing the latest attachment

[jira] [Updated] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1736: Attachment: SENTRY-1736.003-sentry-ha-redesign.patch > Generic service

[jira] [Commented] (SENTRY-1705) Do not start HMSFollower if Hive isn't configured

[ https://issues.apache.org/jira/browse/SENTRY-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016364#comment-16016364 ] Hadoop QA commented on SENTRY-1705: --- Here are the results of testing the latest attachment

[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: Attachment: SENTRY-1761.004-sentry-ha-redesign.patch > Add test for

[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: Attachment: (was: SENTRY-1761.004-sentry-ha-redesign.patch) > Add test

[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: Attachment: SENTRY-1761.004-sentry-ha-redesign.patch > Add test for

[jira] [Resolved] (SENTRY-1747) HMSFollower shouldn't create local hive during tests

[ https://issues.apache.org/jira/browse/SENTRY-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-1747. --- Resolution: Fixed This is resolved by sentry-1757 > HMSFollower shouldn't create local hive during tests >

[jira] [Resolved] (SENTRY-1723) HDFS e2e tests should wait for HMSFollower to start

[ https://issues.apache.org/jira/browse/SENTRY-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-1723. --- Resolution: Fixed sentry-1757 has fixed the issue by changing service orders in test, and make it the same

[jira] [Updated] (SENTRY-1705) Do not start HMSFollower if Hive isn't configured

[ https://issues.apache.org/jira/browse/SENTRY-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1705: -- Attachment: SENTRY-1705.005-sentry-ha-redesign.patch v5. Add util function to get metastore URI > Do not

[jira] [Commented] (SENTRY-1773) Delta change cleaner should leave way more then a single entry intact

[ https://issues.apache.org/jira/browse/SENTRY-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016123#comment-16016123 ] kalyan kumar kalvagadda commented on SENTRY-1773: - I'm not aware of such a use case. >

[jira] [Commented] (SENTRY-1773) Delta change cleaner should leave way more then a single entry intact

[ https://issues.apache.org/jira/browse/SENTRY-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016084#comment-16016084 ] kalyan kumar kalvagadda commented on SENTRY-1773: - Clean up should be based on the

[jira] [Commented] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016047#comment-16016047 ] Hadoop QA commented on SENTRY-1580: --- Here are the results of testing the latest attachment

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015977#comment-16015977 ] kalyan kumar kalvagadda commented on SENTRY-1736: - Should sentry clients perform

[jira] [Commented] (SENTRY-1736) Generic service client should support Kerberos

[ https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015975#comment-16015975 ] kalyan kumar kalvagadda commented on SENTRY-1736: - *Issue created by the missing code and

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015926#comment-16015926 ] kalyan kumar kalvagadda commented on SENTRY-1669: - With the new changes, Sentry requests

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015916#comment-16015916 ] Alexander Kolbasov commented on SENTRY-1669: [~kkalyan] Thank you for the clear summary. 1)

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015900#comment-16015900 ] kalyan kumar kalvagadda commented on SENTRY-1669: - *Test Environment:* HMS has a default

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015899#comment-16015899 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachment

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Attachment: SENTRY-1580.002-sentry-ha-redesign.patch > Provide pooled client

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Status: Patch Available (was: Open) > Provide pooled client connection model with

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Status: Open (was: Patch Available) > Provide pooled client connection model with

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Attachment: (was: SENTRY-1580.002-sentry-ha-redesign.patch) > Provide pooled

[jira] [Updated] (SENTRY-1235) Some pom changes

[ https://issues.apache.org/jira/browse/SENTRY-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-1235: Resolution: Fixed Status: Resolved (was: Patch Available) > Some pom

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.016-sentry-ha-redesign.patch > HMSFollower should

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: (was: SENTRY-1669.016-sentry-ha-redesign.patch) >

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015794#comment-16015794 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachment

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.016-sentry-ha-redesign.patch > HMSFollower should

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: (was: SENTRY-1669.016-sentry-ha-redesign.patch) >

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.016-sentry-ha-redesign.patch > HMSFollower should

[jira] [Updated] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: (was: SENTRY-1669.016-sentry-ha-redesign.patch) >

[jira] [Updated] (SENTRY-1516) Add gpg configuration to the root pom to enable deployment to Maven Central

[ https://issues.apache.org/jira/browse/SENTRY-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-1516: Resolution: Fixed Status: Resolved (was: Patch Available) > Add gpg

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Status: Patch Available (was: Open) > Provide pooled client connection model with

[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA

[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Status: Open (was: Patch Available) > Provide pooled client connection model with

[jira] [Commented] (SENTRY-1771) HDFS client requests full permission update multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015343#comment-16015343 ] Alexander Kolbasov commented on SENTRY-1771: This is likely to be caused by SENTRY-1773 >

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015344#comment-16015344 ] Hadoop QA commented on SENTRY-1772: --- Here are the results of testing the latest attachment

[jira] [Created] (SENTRY-1773) Delta change cleaner should leave way more then a single entry intact

Alexander Kolbasov created SENTRY-1773: -- Summary: Delta change cleaner should leave way more then a single entry intact Key: SENTRY-1773 URL: https://issues.apache.org/jira/browse/SENTRY-1773

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Attachment: SENTRY-1772.001-sentry-ha-redesign.patch > Permissions created before

[jira] [Updated] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1772: --- Status: Patch Available (was: In Progress) > Permissions created before table

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015312#comment-16015312 ] Alexander Kolbasov commented on SENTRY-1772: The problem is with this function: {code}

[jira] [Commented] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015308#comment-16015308 ] Alexander Kolbasov commented on SENTRY-1772: One interesting observation - The original

[jira] [Created] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

Alexander Kolbasov created SENTRY-1772: -- Summary: Permissions created before table creation are not reflected in HDFS ACLs Key: SENTRY-1772 URL: https://issues.apache.org/jira/browse/SENTRY-1772

[jira] [Assigned] (SENTRY-1772) Permissions created before table creation are not reflected in HDFS ACLs

[ https://issues.apache.org/jira/browse/SENTRY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reassigned SENTRY-1772: -- Assignee: Alexander Kolbasov > Permissions created before table creation are