[
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
[
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
>
[
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
>
[
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
[
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
[
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
[
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
[
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
[
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
[
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,
[
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
[
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
[
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
[
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.
>
[
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
[
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
[
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
>
[
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
[
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
[
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
[
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
[
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
[
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?
>
[
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
[
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
[
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
>
[
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.
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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:
[
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
[
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
[
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()
>
[
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
[
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
[
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
[
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
[
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
[
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
[
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.
>
[
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
[
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
[
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
[
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
>
[
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
[
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
[
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
[
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
[
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
[
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 -
[
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.
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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.
[
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()
[
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
[
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
[
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
[
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
[
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
>
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:
[
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
>
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
>
[
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
[
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
>
[
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
[
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
[
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
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 - 100 of 1401 matches
Mail list logo