[jira] [Updated] (SENTRY-1904) TransactionManager should limit the max time spent by transaction retry

[ https://issues.apache.org/jira/browse/SENTRY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1904: Attachment: (was: SENTRY-1904.001.patch) > TransactionManager should

[jira] [Updated] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

[ https://issues.apache.org/jira/browse/SENTRY-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2126: Status: Patch Available (was: In Progress) > Transactional retry not

[jira] [Updated] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

[ https://issues.apache.org/jira/browse/SENTRY-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2126: Attachment: SENTRY-2126.001.patch > Transactional retry not needed for JDO

[jira] [Updated] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

[ https://issues.apache.org/jira/browse/SENTRY-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2126: Description: Transactional reties not needed for failures while persisting

[jira] [Updated] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

[ https://issues.apache.org/jira/browse/SENTRY-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2126: Description: Transactional reties not needed for failures while persisting

[jira] [Updated] (SENTRY-1904) TransactionManager should limit the max time spent by transaction retry

[ https://issues.apache.org/jira/browse/SENTRY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1904: Status: Patch Available (was: In Progress) > TransactionManager should

[jira] [Updated] (SENTRY-1904) TransactionManager should limit the max time spent by transaction retry

[ https://issues.apache.org/jira/browse/SENTRY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1904: Attachment: SENTRY-1904.001.patch > TransactionManager should limit the

[jira] [Assigned] (SENTRY-1904) TransactionManager should limit the max time spent by transaction retry

[ https://issues.apache.org/jira/browse/SENTRY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-1904: --- Assignee: kalyan kumar kalvagadda > TransactionManager should limit

[jira] [Commented] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

[ https://issues.apache.org/jira/browse/SENTRY-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332938#comment-16332938 ] kalyan kumar kalvagadda commented on SENTRY-2126: - FYI [~spena], [~vspec...@gmail.com],

[jira] [Created] (SENTRY-2126) Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID

kalyan kumar kalvagadda created SENTRY-2126: --- Summary: Transactional retry not needed for JDO exceptions on SENTRY_HMS_NOTIFICATION_ID Key: SENTRY-2126 URL:

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync and handle gaps and out-of-sequence notifications.

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.007.patch > Fix the logic of identifying HMS out

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync and handle gaps and out-of-sequence notifications.

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Summary: Fix the logic of identifying HMS out of Sync and handle gaps and

[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Resolution: Fixed Status: Resolved (was: Patch Available) > Add

[jira] [Commented] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327785#comment-16327785 ] kalyan kumar kalvagadda commented on SENTRY-2034: - [~lina.li] and [~spena] Thanks for the

[jira] [Commented] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.

[ https://issues.apache.org/jira/browse/SENTRY-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324549#comment-16324549 ] kalyan kumar kalvagadda commented on SENTRY-2115: - I prefer option-1 listed above. I will

[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Attachment: SENTRY-2034.007.patch > Add e2e tests for testing HMS

[jira] [Commented] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.

[ https://issues.apache.org/jira/browse/SENTRY-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322610#comment-16322610 ] kalyan kumar kalvagadda commented on SENTRY-2115: - There are couple of ways to solve this

[jira] [Commented] (SENTRY-2121) Notifications processed during times when HDFS sync is disabled will not be applied as ACLs when later HDFS sync was to be enabled

[ https://issues.apache.org/jira/browse/SENTRY-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322597#comment-16322597 ] kalyan kumar kalvagadda commented on SENTRY-2121: - [~lina.li] and [~arjunmishra13] This

[jira] [Updated] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.

[ https://issues.apache.org/jira/browse/SENTRY-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2115: Description: On disabling HDFS sync, HMSFollower would update the

[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322407#comment-16322407 ] kalyan kumar kalvagadda commented on SENTRY-2119: - [~lina.li] Notification processor

[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318710#comment-16318710 ] kalyan kumar kalvagadda commented on SENTRY-2119: - [~spena][~arjunmishra13][~lina.li] FYI

[jira] [Comment Edited] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317338#comment-16317338 ] kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:34 PM:

[jira] [Comment Edited] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317338#comment-16317338 ] kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:34 PM:

[jira] [Comment Edited] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317338#comment-16317338 ] kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:33 PM:

[jira] [Comment Edited] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317338#comment-16317338 ] kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:33 PM:

[jira] [Comment Edited] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317254#comment-16317254 ] kalyan kumar kalvagadda edited comment on SENTRY-2119 at 1/8/18 11:30 PM:

[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317338#comment-16317338 ] kalyan kumar kalvagadda commented on SENTRY-2119: - *Approach-2:* As we process the

[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317254#comment-16317254 ] kalyan kumar kalvagadda commented on SENTRY-2119: - *Solution Approach:* When ever

[jira] [Commented] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

[ https://issues.apache.org/jira/browse/SENTRY-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317255#comment-16317255 ] kalyan kumar kalvagadda commented on SENTRY-2119: - [~vspec...@gmail.com] FYI >

[jira] [Created] (SENTRY-2119) HMSFollower may not fetch HMS notifications which are out of order

kalyan kumar kalvagadda created SENTRY-2119: --- Summary: HMSFollower may not fetch HMS notifications which are out of order Key: SENTRY-2119 URL: https://issues.apache.org/jira/browse/SENTRY-2119

[jira] [Created] (SENTRY-2117) event-id in notification log are wrongly called as notification id

kalyan kumar kalvagadda created SENTRY-2117: --- Summary: event-id in notification log are wrongly called as notification id Key: SENTRY-2117 URL: https://issues.apache.org/jira/browse/SENTRY-2117

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312048#comment-16312048 ] kalyan kumar kalvagadda commented on SENTRY-2109: - We need code change done for

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311974#comment-16311974 ] kalyan kumar kalvagadda commented on SENTRY-2109: - [~lina.li] we can increase that number

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.004.patch > Fix the logic of identifying HMS out

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311782#comment-16311782 ] kalyan kumar kalvagadda commented on SENTRY-2109: - [~lina.li] Purging is not an issue as

[jira] [Commented] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311777#comment-16311777 ] kalyan kumar kalvagadda commented on SENTRY-2113: - [~spena] As event-id in the

[jira] [Updated] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2113: Attachment: SENTRY-2113.003.patch > MSentryHmsNotification should also

[jira] [Commented] (SENTRY-2114) Fix behavior of HMSFollower when HDFS sync is not enabled

[ https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311661#comment-16311661 ] kalyan kumar kalvagadda commented on SENTRY-2114: - [~lina.li],[~spena] Even when HDFS

[jira] [Updated] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2113: Description: Currently MSentryHmsNotification is holding notification-id

[jira] [Comment Edited] (SENTRY-2114) Fix behavior of HMSFollower when HDFS sync is not enabled

[ https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310384#comment-16310384 ] kalyan kumar kalvagadda edited comment on SENTRY-2114 at 1/4/18 2:33 PM:

[jira] [Updated] (SENTRY-2085) Sentry error handling exposes SentryGroupNotFoundException externally

[ https://issues.apache.org/jira/browse/SENTRY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2085: Resolution: Fixed Fix Version/s: 2.1.0 Status: Resolved

[jira] [Commented] (SENTRY-2085) Sentry error handling exposes SentryGroupNotFoundException externally

[ https://issues.apache.org/jira/browse/SENTRY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310434#comment-16310434 ] kalyan kumar kalvagadda commented on SENTRY-2085: - [~zamsden_impala_ad21] Thanks for the

[jira] [Created] (SENTRY-2115) Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization.

kalyan kumar kalvagadda created SENTRY-2115: --- Summary: Sentry will be out of sync with HMS on disabling and enabling HDFS synchronization. Key: SENTRY-2115 URL:

[jira] [Commented] (SENTRY-2114) Fix behavior of HMSFollower when HDFS sync is not enabled

[ https://issues.apache.org/jira/browse/SENTRY-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310384#comment-16310384 ] kalyan kumar kalvagadda commented on SENTRY-2114: - [~lina.li] Even the current code

[jira] [Updated] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2113: Attachment: SENTRY-2113.002.patch > MSentryHmsNotification should also

[jira] [Created] (SENTRY-2114) Fix behavior of HMSFollower when HDFS sync is not enabled

kalyan kumar kalvagadda created SENTRY-2114: --- Summary: Fix behavior of HMSFollower when HDFS sync is not enabled Key: SENTRY-2114 URL: https://issues.apache.org/jira/browse/SENTRY-2114

[jira] [Updated] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2113: Attachment: SENTRY-2113.001.patch > MSentryHmsNotification should also

[jira] [Updated] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

[ https://issues.apache.org/jira/browse/SENTRY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2113: Status: Patch Available (was: In Progress) > MSentryHmsNotification

[jira] [Updated] (SENTRY-2085) Sentry error handling exposes SentryGroupNotFoundException externally

[ https://issues.apache.org/jira/browse/SENTRY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2085: Attachment: SENTRY-2085.006.patch > Sentry error handling exposes

[jira] [Commented] (SENTRY-2108) createFullSnapshot so frequently

[ https://issues.apache.org/jira/browse/SENTRY-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308487#comment-16308487 ] kalyan kumar kalvagadda commented on SENTRY-2108: - [~HuanWang] This is definitely as bug.

[jira] [Created] (SENTRY-2113) MSentryHmsNotification should also hold the notification hash

kalyan kumar kalvagadda created SENTRY-2113: --- Summary: MSentryHmsNotification should also hold the notification hash Key: SENTRY-2113 URL: https://issues.apache.org/jira/browse/SENTRY-2113

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.003.patch > Fix the logic of identifying HMS out

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.003.patch > Fix the logic of identifying HMS out

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.002.patch > Fix the logic of identifying HMS out

[jira] [Comment Edited] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305618#comment-16305618 ] kalyan kumar kalvagadda edited comment on SENTRY-2109 at 12/28/17 6:08 PM:

[jira] [Comment Edited] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305618#comment-16305618 ] kalyan kumar kalvagadda edited comment on SENTRY-2109 at 12/28/17 6:08 PM:

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305618#comment-16305618 ] kalyan kumar kalvagadda commented on SENTRY-2109: - *Here is the assumption that

[jira] [Commented] (SENTRY-2106) Sentry ahead full snapshot retry logic

[ https://issues.apache.org/jira/browse/SENTRY-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305572#comment-16305572 ] kalyan kumar kalvagadda commented on SENTRY-2106: - [~arjunmishra13] I have couple of

[jira] [Commented] (SENTRY-2103) Authorization check for CREATEALIAS command doesn't check permissions for the alias name

[ https://issues.apache.org/jira/browse/SENTRY-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305526#comment-16305526 ] kalyan kumar kalvagadda commented on SENTRY-2103: - [~hgadre] Code changes look good.

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Status: Patch Available (was: In Progress) > Fix the logic of identifying

[jira] [Comment Edited] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302476#comment-16302476 ] kalyan kumar kalvagadda edited comment on SENTRY-2109 at 12/23/17 3:01 PM:

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302476#comment-16302476 ] kalyan kumar kalvagadda commented on SENTRY-2109: - I have attached a patch to fix the

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: SENTRY-2109.001.patch > Fix the logic of identifying HMS out

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301807#comment-16301807 ] kalyan kumar kalvagadda commented on SENTRY-2109: - [~vspec...@gmail.com] Sure, I will add

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301666#comment-16301666 ] kalyan kumar kalvagadda commented on SENTRY-2109: - Working on a patch to avoid the

[jira] [Updated] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2109: Attachment: Screenshot_HMS_NOTIFICATION_LOG.png > Fix the logic of

[jira] [Commented] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

[ https://issues.apache.org/jira/browse/SENTRY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301652#comment-16301652 ] kalyan kumar kalvagadda commented on SENTRY-2109: - With this below logic HMSFollower

[jira] [Created] (SENTRY-2109) Fix the logic of identifying HMS out of Sync

kalyan kumar kalvagadda created SENTRY-2109: --- Summary: Fix the logic of identifying HMS out of Sync Key: SENTRY-2109 URL: https://issues.apache.org/jira/browse/SENTRY-2109 Project: Sentry

[jira] [Commented] (SENTRY-2105) Add impersonator info to Solr audit logs

[ https://issues.apache.org/jira/browse/SENTRY-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300146#comment-16300146 ] kalyan kumar kalvagadda commented on SENTRY-2105: - This issue can not be fixed with out

[jira] [Commented] (SENTRY-2097) Sentry privileges model: Can Sentry take a database privileges away from a server privileges?

[ https://issues.apache.org/jira/browse/SENTRY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295731#comment-16295731 ] kalyan kumar kalvagadda commented on SENTRY-2097: - Jest for reference

[jira] [Comment Edited] (SENTRY-2097) Sentry privileges model: Can Sentry take a database privileges away from a server privileges?

[ https://issues.apache.org/jira/browse/SENTRY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295731#comment-16295731 ] kalyan kumar kalvagadda edited comment on SENTRY-2097 at 12/18/17 9:53 PM:

[jira] [Comment Edited] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286336#comment-16286336 ] kalyan kumar kalvagadda edited comment on SENTRY-2034 at 12/11/17 5:47 PM:

[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Attachment: (was: SENTRY-2034.005.patch) > Add e2e tests for testing

[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Attachment: SENTRY-2034.005.patch > Add e2e tests for testing HMS

[jira] [Commented] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286336#comment-16286336 ] kalyan kumar kalvagadda commented on SENTRY-2034: - I have re-submitted the patch as the

[jira] [Comment Edited] (SENTRY-2096) Fail unit tests at end

[ https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285936#comment-16285936 ] kalyan kumar kalvagadda edited comment on SENTRY-2096 at 12/11/17 1:53 PM:

[jira] [Commented] (SENTRY-2096) Fail unit tests at end

[ https://issues.apache.org/jira/browse/SENTRY-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285936#comment-16285936 ] kalyan kumar kalvagadda commented on SENTRY-2096: - --fail-at-end is not limited to tests.

[jira] [Commented] (SENTRY-2004) Create Release-2.0.0

[ https://issues.apache.org/jira/browse/SENTRY-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282457#comment-16282457 ] kalyan kumar kalvagadda commented on SENTRY-2004: - release-2.0.0 is ready and the voting

[jira] [Created] (SENTRY-2093) Close JIRA version for 2.0.0

kalyan kumar kalvagadda created SENTRY-2093: --- Summary: Close JIRA version for 2.0.0 Key: SENTRY-2093 URL: https://issues.apache.org/jira/browse/SENTRY-2093 Project: Sentry Issue

[jira] [Resolved] (SENTRY-2004) Create Release-2.0.0

[ https://issues.apache.org/jira/browse/SENTRY-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda resolved SENTRY-2004. - Resolution: Fixed > Create Release-2.0.0 > > >

[jira] [Resolved] (SENTRY-2005) Run vote on Release-2.0.0

[ https://issues.apache.org/jira/browse/SENTRY-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda resolved SENTRY-2005. - Resolution: Fixed Assignee: kalyan kumar kalvagadda Voting process

[jira] [Assigned] (SENTRY-2004) Create Release-2.0.0

[ https://issues.apache.org/jira/browse/SENTRY-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-2004: --- Assignee: kalyan kumar kalvagadda > Create Release-2.0.0 >

[jira] [Updated] (SENTRY-2034) Add e2e tests for testing HMS notification processing.

[ https://issues.apache.org/jira/browse/SENTRY-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2034: Attachment: SENTRY-2034.005.patch > Add e2e tests for testing HMS

[jira] [Commented] (SENTRY-2086) Sentry distribution source does not build to to missing modules

[ https://issues.apache.org/jira/browse/SENTRY-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277113#comment-16277113 ] kalyan kumar kalvagadda commented on SENTRY-2086: - [~coheig] sure, I will send a mail

[jira] [Commented] (SENTRY-2086) Sentry distribution source does not build to to missing modules

[ https://issues.apache.org/jira/browse/SENTRY-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277103#comment-16277103 ] kalyan kumar kalvagadda commented on SENTRY-2086: - +1 . It works with this change. >

[jira] [Commented] (SENTRY-2081) Automate the generation LICENSE.txt based on distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276783#comment-16276783 ] kalyan kumar kalvagadda commented on SENTRY-2081: - [~coheig], [~spena], [~akolb], Thanks

[jira] [Commented] (SENTRY-2084) Exclude javax.jms:jms from sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276780#comment-16276780 ] kalyan kumar kalvagadda commented on SENTRY-2084: - [~spena] Thanks for the review. >

[jira] [Updated] (SENTRY-2081) Automate the generation LICENSE.txt based on distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2081: Resolution: Fixed Status: Resolved (was: Patch Available) >

[jira] [Updated] (SENTRY-2076) Some test artifacts are not defined at test scope

[ https://issues.apache.org/jira/browse/SENTRY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2076: Affects Version/s: 2.1.0 2.0.0 > Some test

[jira] [Updated] (SENTRY-2076) Some test artifacts are not defined at test scope

[ https://issues.apache.org/jira/browse/SENTRY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2076: Fix Version/s: 2.1.0 > Some test artifacts are not defined at test scope >

[jira] [Updated] (SENTRY-2082) Exclude javax.servlet-3.0.0.v201112011016.jar from Sentry dist

[ https://issues.apache.org/jira/browse/SENTRY-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2082: Fix Version/s: 2.1.0 > Exclude javax.servlet-3.0.0.v201112011016.jar from

[jira] [Updated] (SENTRY-2079) Sentry HA leader monitor does not work due to a mix of curator versions in the classpath

[ https://issues.apache.org/jira/browse/SENTRY-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2079: Fix Version/s: 2.1.0 > Sentry HA leader monitor does not work due to a mix

[jira] [Updated] (SENTRY-2081) Automate the generation LICENSE.txt based on distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2081: Fix Version/s: 2.1.0 2.0.0 > Automate the generation

[jira] [Updated] (SENTRY-2084) Exclude javax.jms:jms from sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2084: Resolution: Fixed Fix Version/s: 2.1.0 2.0.0

[jira] [Updated] (SENTRY-2084) Exclude javax.jms:jms from sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2084: Status: Patch Available (was: In Progress) > Exclude javax.jms:jms from

[jira] [Updated] (SENTRY-2081) Automate the generation LICENSE.txt based on distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2081: Description: As per https://www.apache.org/dev/licensing-howto.html ,

[jira] [Updated] (SENTRY-2081) Automate the generation LICENSE.txt based on distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2081: Summary: Automate the generation LICENSE.txt based on distributed jars

[jira] [Updated] (SENTRY-2084) Exclude javax.jms:jms from sentry distribution

[ https://issues.apache.org/jira/browse/SENTRY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2084: Attachment: SENTRY-2084.001.patch > Exclude javax.jms:jms from sentry

[jira] [Created] (SENTRY-2084) Exclude javax.jms:jms from sentry distribution

kalyan kumar kalvagadda created SENTRY-2084: --- Summary: Exclude javax.jms:jms from sentry distribution Key: SENTRY-2084 URL: https://issues.apache.org/jira/browse/SENTRY-2084 Project: Sentry

[jira] [Updated] (SENTRY-2081) Update the LICENSE.txt with the license information of distributed jars

[ https://issues.apache.org/jira/browse/SENTRY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-2081: Attachment: SENTRY-2081.008.patch > Update the LICENSE.txt with the

<    5   6   7   8   9   10   11   12   13   14   >