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

2017-05-18 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016040#comment-16016040 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-18 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015926#comment-16015926 ] kalyan kumar kalvagadda commented on SENTRY-1669: - With the new changes,

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

2017-05-18 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015916#comment-16015916 ] Alexander Kolbasov commented on SENTRY-1669: [~kkalyan] Thank you for the cle

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

2017-05-18 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015900#comment-16015900 ] kalyan kumar kalvagadda commented on SENTRY-1669: - *Test Environment:* HM

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

2017-05-18 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015899#comment-16015899 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-18 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015794#comment-16015794 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-17 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015109#comment-16015109 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-17 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014947#comment-16014947 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-17 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014941#comment-16014941 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-17 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014907#comment-16014907 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-17 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014707#comment-16014707 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-16 Thread Hadoop QA (JIRA)
[ 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-1669) HMSFollower should read current processed notification ID from database every time it runs

2017-05-16 Thread Hadoop QA (JIRA)
[ 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] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

2017-05-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011573#comment-16011573 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011352#comment-16011352 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011011#comment-16011011 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-12 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008637#comment-16008637 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-12 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008446#comment-16008446 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-11 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006573#comment-16006573 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-11 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006365#comment-16006365 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005713#comment-16005713 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-10 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005475#comment-16005475 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-10 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005265#comment-16005265 ] kalyan kumar kalvagadda commented on SENTRY-1669: - @hahao Attached patch

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

2017-05-10 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005253#comment-16005253 ] Hao Hao commented on SENTRY-1669: - [~kkalyan] Can you update the patch based on current b

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

2017-05-09 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003831#comment-16003831 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-09 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003814#comment-16003814 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-09 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003815#comment-16003815 ] kalyan kumar kalvagadda commented on SENTRY-1669: - Considering the issues

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

2017-05-09 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002992#comment-16002992 ] Alexander Kolbasov commented on SENTRY-1669: The notification id stored in Se

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

2017-05-08 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001871#comment-16001871 ] Alexander Kolbasov commented on SENTRY-1669: Imagine two threads. Both start

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

2017-05-08 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001831#comment-16001831 ] kalyan kumar kalvagadda commented on SENTRY-1669: - Even if HMSFollower is

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

2017-05-08 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001819#comment-16001819 ] Alexander Kolbasov commented on SENTRY-1669: Usually HMSFollower is the only

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

2017-05-08 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001818#comment-16001818 ] Alexander Kolbasov commented on SENTRY-1669: I think the suggested approach d

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

2017-05-08 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001814#comment-16001814 ] kalyan kumar kalvagadda commented on SENTRY-1669: - HMSFollower is the onl

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

2017-05-08 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001802#comment-16001802 ] Alexander Kolbasov commented on SENTRY-1669: [~kkalyan] What would happen in

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

2017-05-08 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001791#comment-16001791 ] Alexander Kolbasov commented on SENTRY-1669: [~kkalyan] Can you clarify your

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

2017-05-03 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995643#comment-15995643 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-03 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995373#comment-15995373 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-05-03 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995356#comment-15995356 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

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

2017-04-28 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988962#comment-15988962 ] kalyan kumar kalvagadda commented on SENTRY-1669: - HMS follower periodica

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975698#comment-15975698 ] Na Li commented on SENTRY-1669: --- [~kkalyan] Can you be more specific on what else to change

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

2017-04-19 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975688#comment-15975688 ] kalyan kumar kalvagadda commented on SENTRY-1669: - There will be some mor

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975436#comment-15975436 ] Na Li commented on SENTRY-1669: --- Can be solved by changes in SENTRY-1649 > HMSFollower sho

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975435#comment-15975435 ] Na Li commented on SENTRY-1669: --- this issue can be fixed by changes in Sentry-1649 (to allo