[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Attachment: SENTRY-1743.001.patch > Two SentryStore instances are one too many >

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Patch Available (was: Open) > Two SentryStore instances are one too many > -

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Open (was: Patch Available) > Two SentryStore instances are one too many > -

[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 HA

[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 connecti

[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 HA

[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 clie

[jira] [Commented] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

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

[jira] [Updated] (SENTRY-1768) Avoid detaching object on transaction exit when it isn't needed

[ https://issues.apache.org/jira/browse/SENTRY-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1768: --- Attachment: SENTRY-1768.001-sentry-ha-redesign.patch > Avoid detaching object on tran

[jira] [Updated] (SENTRY-1768) Avoid detaching object on transaction exit when it isn't needed

[ https://issues.apache.org/jira/browse/SENTRY-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1768: --- Status: Patch Available (was: Open) > Avoid detaching object on transaction exit whe

[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&focusedCommentId=16013546#comment-16013546 ] Hadoop QA commented on SENTRY-1580: --- Here are the results of testing the latest attachm

[jira] [Created] (SENTRY-1768) Avoid detaching object on transaction exit when it isn't needed

Alexander Kolbasov created SENTRY-1768: -- Summary: Avoid detaching object on transaction exit when it isn't needed Key: SENTRY-1768 URL: https://issues.apache.org/jira/browse/SENTRY-1768 Project:

[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 HA

[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 HA

[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 connecti

[jira] [Updated] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

[ https://issues.apache.org/jira/browse/SENTRY-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1757: -- Attachment: SENTRY-1757.007-sentry-ha-redesign.patch v7. Change how the services are started to avoid connectio

[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&focusedCommentId=16013231#comment-16013231 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

[jira] [Commented] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

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

[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.012-sentry-ha-redesign.patch > HMSFollower should r

[jira] [Updated] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

[ https://issues.apache.org/jira/browse/SENTRY-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1757: -- Attachment: SENTRY-1757.006-sentry-ha-redesign.patch v6. re-trigger the build. build 2716 had build issue. > A

[jira] [Updated] (SENTRY-1767) Multiple followers should not create full snapshot

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

[jira] [Updated] (SENTRY-1767) Multiple followers should not create full snapshot

[ https://issues.apache.org/jira/browse/SENTRY-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1767: --- Affects Version/s: (was: 1.8.0) > Multiple followers should not create full snaps

[jira] [Updated] (SENTRY-1767) Multiple followers should not create full snapshot

[ https://issues.apache.org/jira/browse/SENTRY-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1767: --- Issue Type: Sub-task (was: Bug) Parent: SENTRY-872 > Multiple followers shou

[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&focusedCommentId=16012951#comment-16012951 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

[jira] [Created] (SENTRY-1767) Multiple followers should not create full snapshot

kalyan kumar kalvagadda created SENTRY-1767: --- Summary: Multiple followers should not create full snapshot Key: SENTRY-1767 URL: https://issues.apache.org/jira/browse/SENTRY-1767 Project: Sent

[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&focusedCommentId=16012949#comment-16012949 ] Alexander Kolbasov commented on SENTRY-1580: A short summary of the change.

[jira] [Commented] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

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

[jira] [Commented] (SENTRY-296) Sentry Service Client does not allow for connection pooling

[ https://issues.apache.org/jira/browse/SENTRY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012915#comment-16012915 ] Alexander Kolbasov commented on SENTRY-296: --- SENTRY-1580 provides a different wa

[jira] [Updated] (SENTRY-1757) Avoid using local hive meta store with wrong configuration

[ https://issues.apache.org/jira/browse/SENTRY-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1757: -- Attachment: SENTRY-1757.006-sentry-ha-redesign.patch v6. Update based on review. Add more comments > Avoid usi

[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.001-sentry-ha-redesign.patch > Generic service clie

[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.011-sentry-ha-redesign.patch > HMSFollower should r

[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.011-sentry-ha-redesign.patch) > HMSFollow

[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.011-sentry-ha-redesign.patch) > HMSFollow

[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.011-sentry-ha-redesign.patch > HMSFollower should r

[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.011-sentry-ha-redesign.patch) > HMSFollow

[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.011-sentry-ha-redesign.patch > HMSFollower should r

[jira] [Updated] (SENTRY-1716) HMSFollower doesn't need to save path info when HDFS sync is disabled

[ https://issues.apache.org/jira/browse/SENTRY-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1716: --- Resolution: Fixed Status: Resolved (was: Patch Available) [~spena] Thank you

[jira] [Commented] (SENTRY-1716) HMSFollower doesn't need to save path info when HDFS sync is disabled

[ https://issues.apache.org/jira/browse/SENTRY-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012530#comment-16012530 ] Sergio Peña commented on SENTRY-1716: - [~akolb] The latest patch from RB is already a