[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

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

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973198#comment-15973198 ] Alexander Kolbasov commented on SENTRY-1674: Transferring +1 from reviewboard. > HMSFollower

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973203#comment-15973203 ] kalyan kumar kalvagadda commented on SENTRY-1674: - Fix for this issue is already

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973273#comment-15973273 ] Hao Hao commented on SENTRY-1674: - Agree with [~kkalyan] No need to introduce a new variable to record

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Attachment: (was: SENTRY-1587.patch) > Refactor SentryStore transaction to persist a single path

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Attachment: SENTRY-1587.001-sentry-ha-redesign.patch > Refactor SentryStore transaction to persist a

[jira] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone

[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973322#comment-15973322 ] Hao Hao commented on SENTRY-1643: - [~eddyxu] Do we still need to have {{value-strategy="increment"}} for

[jira] [Commented] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

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

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Attachment: (was: SENTRY-1587.001-sentry-ha-redesign.patch) > Refactor SentryStore transaction to

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973315#comment-15973315 ] kalyan kumar kalvagadda commented on SENTRY-1674: - [~akolb] Issue that we trying to

[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

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

[jira] [Created] (SENTRY-1707) Add unit test to check response from HiveMetaStoreClient.getNextNotification when there is no new notification at Hive meta store

Na Li created SENTRY-1707: - Summary: Add unit test to check response from HiveMetaStoreClient.getNextNotification when there is no new notification at Hive meta store Key: SENTRY-1707 URL:

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973300#comment-15973300 ] Alexander Kolbasov commented on SENTRY-1674: [~kkalyan] [~hahao] The purpose of this JIRA is

[jira] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone

[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973456#comment-15973456 ] Lei (Eddy) Xu commented on SENTRY-1643: --- [~hahao] We dont need it now. > AutoIncrement ChangeID

[jira] [Created] (SENTRY-1706) Remove value-strategy for delta change tables.

Lei (Eddy) Xu created SENTRY-1706: - Summary: Remove value-strategy for delta change tables. Key: SENTRY-1706 URL: https://issues.apache.org/jira/browse/SENTRY-1706 Project: Sentry Issue

[jira] [Commented] (SENTRY-1593) Implement client failover for Generic and NN clients

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

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Attachment: SENTRY-1587.001-sentry-ha-redesign.patch > Refactor SentryStore transaction to persist a

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Attachment: (was: SENTRY-1587.001-sentry-ha-redesign.patch) > Refactor SentryStore transaction to

[jira] [Updated] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

[ https://issues.apache.org/jira/browse/SENTRY-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1587: Status: Patch Available (was: Open) > Refactor SentryStore transaction to persist a single path

[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients

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

[jira] [Commented] (SENTRY-1587) Refactor SentryStore transaction to persist a single path transcation bundled with corresponding delta path change

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

[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.021-sentry-ha-redesign.patch move starting HMSfollower to end of runServer(). V21 >

[jira] [Updated] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1674: -- Attachment: SENTRY-1674.005-sentry-ha-redesign.patch simplify logic v5 > HMSFollower shouldn't print the same

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

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