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

2017-04-10 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963455#comment-15963455 ] Na Li commented on SENTRY-1643: --- If the path change and perm change do not happen often, the change from

[jira] [Assigned] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch

2017-04-10 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li reassigned SENTRY-1685: - Assignee: Na Li > Port SENTRY-1489 to sentry-ha-redesign branch >

[jira] [Assigned] (SENTRY-1693) Adding a view with create a notification with empty path. This is not handled properly in HMS follower

2017-04-10 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li reassigned SENTRY-1693: - Assignee: Na Li > Adding a view with create a notification with empty path. This is not handled >

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

2017-04-11 Thread Na Li (JIRA)
[ 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.004-sentry-ha-redesign.patch fix the build error by including all changes in a single

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

2017-04-11 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15964409#comment-15964409 ] Na Li commented on SENTRY-1649: --- My latest update does not destroy one instance. You can take a look at

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-03 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953836#comment-15953836 ] Na Li commented on SENTRY-1614: --- The problem is fixed for me after I apply all of the following changes

[jira] [Comment Edited] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-03 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953836#comment-15953836 ] Na Li edited comment on SENTRY-1614 at 4/3/17 5:13 PM: --- The problem is fixed for me

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955190#comment-15955190 ] Na Li commented on SENTRY-1614: --- in sentry-ha-redesign branch, I have to apply the change

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955442#comment-15955442 ] Na Li commented on SENTRY-1614: --- after I check out master branch (which works without any change), and then

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955521#comment-15955521 ] Na Li commented on SENTRY-1614: --- In order to run the script to initiate schema, I drop the database sentry,

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

2017-04-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955541#comment-15955541 ] Na Li commented on SENTRY-1643: --- What are the scenarios that changeID should be increased by one? Does that

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

2017-04-11 Thread Na Li (JIRA)
[ 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.005-sentry-ha-redesign.patch 1. Implement HMSFollower.close(). Remove its start() and

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

2017-04-11 Thread Na Li (JIRA)
[ 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.006-sentry-ha-redesign.patch version 006 is patch after rebase that includes all

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

2017-04-11 Thread Na Li (JIRA)
[ 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.007-sentry-ha-redesign.patch update for suggestions in code review by Sasha. >

[jira] [Commented] (SENTRY-1681) SentryHdfsServiceException is an unchecked exception

2017-04-06 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959028#comment-15959028 ] Na Li commented on SENTRY-1681: --- "SENTRY-1593 Implement client failover for all the sentry clients" is

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

2017-04-06 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li reassigned SENTRY-1674: - Assignee: Na Li (was: Na Li) > HMSFollower shouldn't print the same value of notification ID multiple

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

2017-04-06 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li reassigned SENTRY-1649: - Assignee: Na Li (was: Na Li) > Initialize HMSFollower when sentry server actually starts >

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

2017-04-06 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Status: Patch Available (was: Open) move the scheduling of HMS follower to runServer(). > Initialize

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

2017-04-06 Thread Na Li (JIRA)
[ 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.002-sentry-ha-redesign.patch update based on code review. change code style and output

[jira] [Commented] (SENTRY-1693) Adding a view with create a notification with empty path. This is not handled properly in HMS follower

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956900#comment-15956900 ] Na Li commented on SENTRY-1693: --- "HMS throws an exception on such notifications" is this "HMS follower

[jira] [Commented] (SENTRY-1693) Adding a view with create a notification with empty path. This is not handled properly in HMS follower

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957418#comment-15957418 ] Na Li commented on SENTRY-1693: --- I guess Sasha means we should catch the exception when applying the

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

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957304#comment-15957304 ] Na Li commented on SENTRY-1649: --- We need to support multiple start/stop of sentry service. Therefore, start

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

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957918#comment-15957918 ] Na Li commented on SENTRY-1649: --- Sorry, I forgot to publish it. Can you check if it is accessible now? >

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-12 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966688#comment-15966688 ] Na Li commented on SENTRY-1614: --- this link is useful for Limits on InnoDB Tables

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

2017-04-12 Thread Na Li (JIRA)
[ 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.008-sentry-ha-redesign.patch change the order of scheduling SentryStoreCleaner, trying

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

2017-04-13 Thread Na Li (JIRA)
[ 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.012-sentry-ha-redesign.patch test build SENTRY-1649.012-sentry-ha-redesign.patch >

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

2017-04-20 Thread Na Li (JIRA)
[ 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.025-sentry-ha-redesign.patch create HMSFollower in constructor and startHMSFollower.

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977318#comment-15977318 ] Na Li edited comment on SENTRY-1649 at 4/20/17 7:28 PM: create HMSFollower in

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

2017-04-20 Thread Na Li (JIRA)
[ 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.024-sentry-ha-redesign.patch > Initialize HMSFollower when sentry server actually

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

2017-04-19 Thread Na Li (JIRA)
[ 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.022-sentry-ha-redesign.patch move start HMSFollower at the start of runServer(). v22

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974749#comment-15974749 ] Na Li commented on SENTRY-1649: --- After moving starting HMSfollower to end of runServer(). the following

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

2017-04-20 Thread Na Li (JIRA)
[ 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.010-sentry-ha-redesign.patch skip processing with no updates. v10 > HMSFollower

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

2017-04-20 Thread Na Li (JIRA)
[ 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.024-sentry-ha-redesign.patch v24 again > Initialize HMSFollower when sentry server

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

2017-04-20 Thread Na Li (JIRA)
[ 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.026-sentry-ha-redesign.patch The same as v24, but rebased on the latest changes in

[jira] [Commented] (SENTRY-1711) HMSFollower shouldn't call processNotificationEvents() unless there are events

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978057#comment-15978057 ] Na Li commented on SENTRY-1711: --- [~akolb] it is already done in HMSFollower at

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

2017-04-21 Thread Na Li (JIRA)
[ 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.026-sentry-ha-redesign.patch v26 again > Initialize HMSFollower when sentry server

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

2017-04-21 Thread Na Li (JIRA)
[ 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.026-sentry-ha-redesign.patch v26 the third time > Initialize HMSFollower when sentry

[jira] [Commented] (SENTRY-1588) Add user level privilege change support for SentryPolicyStorePlugin

2017-04-21 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978920#comment-15978920 ] Na Li commented on SENTRY-1588: --- [~hahao]This is not really HA related. Is that right? > Add user level

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

2017-04-20 Thread Na Li (JIRA)
[ 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.008-sentry-ha-redesign.patch log debug message if the ID has changed. log error

[jira] [Created] (SENTRY-1712) Add capability to force Sentry to get full snapshot from HMS

2017-04-21 Thread Na Li (JIRA)
Na Li created SENTRY-1712: - Summary: Add capability to force Sentry to get full snapshot from HMS Key: SENTRY-1712 URL: https://issues.apache.org/jira/browse/SENTRY-1712 Project: Sentry Issue Type:

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

2017-04-13 Thread Na Li (JIRA)
[ 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.014-sentry-ha-redesign.patch SENTRY-1649.014-sentry-ha-redesign.patch > Initialize

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

2017-04-13 Thread Na Li (JIRA)
[ 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.013-sentry-ha-redesign.patch SENTRY-1649.013-sentry-ha-redesign.patch only call

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

2017-04-13 Thread Na Li (JIRA)
[ 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.009-sentry-ha-redesign.patch shutdown service executor at SentryService.stop() >

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

2017-04-13 Thread Na Li (JIRA)
[ 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.010-sentry-ha-redesign.patch the patch file name is

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

2017-04-13 Thread Na Li (JIRA)
[ 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.011-sentry-ha-redesign.patch SENTRY-1649.011-sentry-ha-redesign.patct create

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975382#comment-15975382 ] Na Li commented on SENTRY-1674: --- There is no conflict between Sentry-1674 and the work around by Hao at

[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=15975436#comment-15975436 ] Na Li commented on SENTRY-1669: --- Can be solved by changes in SENTRY-1649 > HMSFollower should read current

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975452#comment-15975452 ] Na Li commented on SENTRY-1674: --- There are two things to clarify. "Let's focus on this issue. This issue

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

2017-04-20 Thread Na Li (JIRA)
[ 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.023-sentry-ha-redesign.patch attach v23 again to trigger build > Initialize

[jira] [Commented] (SENTRY-1703) Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976919#comment-15976919 ] Na Li commented on SENTRY-1703: --- [~wldata] I will take a look at this issue. Then come back to you. >

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1706: -- Lei, I suspect when you have "value-strategy" on chang_ID, it acquires a lock on the table. So the order of lock

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

2017-04-20 Thread Na Li (JIRA)
[ 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.024-sentry-ha-redesign.patch same as v23, but change version to v24 to trigger build

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976936#comment-15976936 ] Na Li commented on SENTRY-1674: --- I talked with Kalyan. We both agree that right now, we can accept both my

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

2017-04-20 Thread Na Li (JIRA)
[ 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 Patch24 Test fail.txt > Initialize HMSFollower when sentry server actually starts >

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.001-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: Sentry-1649 Patch24 Test fail.txt) > Initialize HMSFollower when sentry server actually

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.024-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.023-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server

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

2017-04-20 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.023-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server

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

2017-04-13 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: lina_test.patch with minor change to get build machine why has "[DEBUG -

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

2017-04-14 Thread Na Li (JIRA)
[ 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.016-sentry-ha-redesign.patch add patch SENTRY-1649.016-sentry-ha-redesign.patch.

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

2017-04-14 Thread Na Li (JIRA)
[ 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.017-sentry-ha-redesign.patch full change patch

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

2017-04-17 Thread Na Li (JIRA)
[ 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.020-sentry-ha-redesign.patch remove extra code with patch v20 > Initialize

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

2017-04-17 Thread Na Li (JIRA)
[ 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.004-sentry-ha-redesign.patch > HMSFollower shouldn't print the same value of

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

2017-04-17 Thread Na Li (JIRA)
[ 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.002-sentry-ha-redesign.patch not log message if there is no change and last log ID is

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

2017-04-17 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1674: -- Status: Patch Available (was: Open) > HMSFollower shouldn't print the same value of notification ID multiple

[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=15975698#comment-15975698 ] Na Li commented on SENTRY-1669: --- [~kkalyan] Can you be more specific on what else to change to make sure

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

2017-04-19 Thread Na Li (JIRA)
[ 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.023-sentry-ha-redesign.patch create HMSFollower in startHMSFollower and await

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

2017-04-19 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975820#comment-15975820 ] Na Li commented on SENTRY-1643: --- based on

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

2017-04-23 Thread Na Li (JIRA)
[ 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.026-sentry-ha-redesign.patch v26 4th times > Initialize HMSFollower when sentry

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

2017-04-21 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-1707. --- Resolution: Won't Fix Sergio is making code changes for HIVE-15761 to return response with empty set to be

[jira] [Commented] (SENTRY-1614) DB schema key is too long for MySQL

2017-04-03 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954041#comment-15954041 ] Na Li commented on SENTRY-1614: --- On master, the schema creation works without my change for Uri_Idx. > DB

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

2017-04-05 Thread Na Li (JIRA)
[ 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.001-sentry-ha-redesign.patch > Initialize HMSFollower when sentry server actually

[jira] [Commented] (SENTRY-378) Clean up the usage of SentryAccessDeniedException

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957730#comment-15957730 ] Na Li commented on SENTRY-378: -- I agree. That is why I commented in review to update the test code. > Clean

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

2017-04-05 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957733#comment-15957733 ] Na Li commented on SENTRY-1649: --- code review link https://reviews.apache.org/r/58221/ > Initialize

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

2017-04-07 Thread Na Li (JIRA)
[ 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.003-sentry-ha-redesign.patch Create HMSFollower instance in SentryService constructor.

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

2017-04-17 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1674: -- Attachment: SENTRY-1649.019-sentry-ha-redesign.patch only call start cleaner in runServer()

[jira] [Commented] (SENTRY-1681) SentryHdfsServiceException is an unchecked exception

2017-04-14 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969529#comment-15969529 ] Na Li commented on SENTRY-1681: --- [~akolb] what SentryHdfsServiceException should derive from? just extends

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

2017-04-14 Thread Na Li (JIRA)
[ 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.018-sentry-ha-redesign.patch some format change

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

2017-04-14 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969523#comment-15969523 ] Na Li commented on SENTRY-1705: --- [~akolb] how to detect Hive is not configured? Can

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

2017-04-17 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1674: -- Attachment: (was: SENTRY-1649.019-sentry-ha-redesign.patch) > HMSFollower shouldn't print the same value

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

2017-04-17 Thread Na Li (JIRA)
[ 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.019-sentry-ha-redesign.patch only start cleaner at runServer in patch version 19 >

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

2017-04-18 Thread Na Li (JIRA)
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] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

2017-04-18 Thread Na Li (JIRA)
[ 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

2017-04-18 Thread Na Li (JIRA)
[ 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-1703) Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout

2017-04-24 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981586#comment-15981586 ] Na Li commented on SENTRY-1703: --- it looks like when Solr has a request, it creates a new sentry client to

[jira] [Updated] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-02 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1854: -- Attachment: SENTRY-1854.004-master.patch v4. no change. just to trigger build. > HMSFollower should handle

[jira] [Updated] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-03 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1854: -- Attachment: SENTRY-1854.005-master.patch v5 on master branch. rebase on latest code > HMSFollower should

[jira] [Updated] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-01 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1854: -- Attachment: SENTRY-1854.002-master.patch v2 on master. Update based on Kalyan comments > HMSFollower should

[jira] [Updated] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-01 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1854: -- Attachment: SENTRY-1854.003-master.patch v3. no change to v2. just to trigger build. > HMSFollower should

[jira] [Commented] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-01 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109825#comment-16109825 ] Na Li commented on SENTRY-1854: --- The failure for v2 on master branch is due to out of memory at building

[jira] [Updated] (SENTRY-1854) HMSFollower should handle notifications even if HDFS sync is disabled.

2017-08-03 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1854: -- Attachment: SENTRY-1854.006-master.patch v6 on master branch. fix test failure > HMSFollower should handle

[jira] [Commented] (SENTRY-1878) Provide support for programmatic fault injections for transactions

2017-08-10 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121748#comment-16121748 ] Na Li commented on SENTRY-1878: --- Vamsee hard-coded the exception in SentryStore.execute(). We can make it

[jira] [Updated] (SENTRY-1855) PERM/PATH transactions can fail to commit to the sentry database under load

2017-08-09 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1855: -- Attachment: SENTRY-1855.001.patch v1 on master. Get perm delta changes using timestamp, not changeID >

[jira] [Commented] (SENTRY-1876) Filter the result of show databases and show tables in hive

2017-08-09 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16121012#comment-16121012 ] Na Li commented on SENTRY-1876: --- [~dongyifeng] Can you create a review at review board

[jira] [Updated] (SENTRY-1856) Persisting HMS snapshot and the notification-id to database in same transaction

2017-08-11 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1856: -- Status: Patch Available (was: Open) > Persisting HMS snapshot and the notification-id to database in same >

[jira] [Updated] (SENTRY-1856) Persisting HMS snapshot and the notification-id to database in same transaction

2017-08-11 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1856: -- Attachment: SENTRY-1856.001.patch v1 on master branch. > Persisting HMS snapshot and the notification-id to

[jira] [Updated] (SENTRY-1856) Persisting HMS snapshot and the notification-id to database in same transaction

2017-08-11 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1856: -- Attachment: SENTRY-1856.002.patch v2. no change. just to trigger build > Persisting HMS snapshot and the

[jira] [Commented] (SENTRY-1883) Optimizing Sentry to HDFS protocol

2017-08-11 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124312#comment-16124312 ] Na Li commented on SENTRY-1883: --- Comments from Brian > >- Rather then streaming huge snapshots in a

[jira] [Created] (SENTRY-1883) Optimizing Sentry to HDFS protocol

2017-08-11 Thread Na Li (JIRA)
Na Li created SENTRY-1883: - Summary: Optimizing Sentry to HDFS protocol Key: SENTRY-1883 URL: https://issues.apache.org/jira/browse/SENTRY-1883 Project: Sentry Issue Type: Improvement

  1   2   3   4   5   6   7   8   9   10   >