[jira] [Created] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
Hao Hao created SENTRY-1643: --- Summary: AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone Key: SENTRY-1643 URL: https://issues.apache.org/jira/browse/SENTRY-1643 Project: Sentry Issue Type: Sub-task Affects Versions: sentry-ha-redesign Reporter: Hao Hao Fix For: sentry-ha-redesign In MSentryPermChange/MSentryPathChange table, the changeID field is auto-increment. However, found through the integration unit test TestHDFSIntegration, the value does not seem to be correctly increased. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: SENTRY-1642.002.patch > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.002.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Patch Available (was: Open) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.002.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: (was: SENTRY-1642.001.patch) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Open (was: Patch Available) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: SENTRY-1613.001-sentry-ha-redesign.patch > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the logic for propagating Sentry Permissions or Sentry representation of > HMS Paths, from a persistent storage instead of in memoery cache of Sentry > service, to a Sentry consumer such as HDFS NameNode. It includes: > * Delta update retrieval logic from persistent storage. > * Propagation logic for consumer to get the delta update or a complete > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: (was: SENTRY-1613.001-sentry-ha-redesign.patch) > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the logic for propagating Sentry Permissions or Sentry representation of > HMS Paths, from a persistent storage instead of in memoery cache of Sentry > service, to a Sentry consumer such as HDFS NameNode. It includes: > * Delta update retrieval logic from persistent storage. > * Propagation logic for consumer to get the delta update or a complete > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: (was: SENTRY-1613.001-sentry-ha-redesign.patch) > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the logic for propagating Sentry Permissions or Sentry representation of > HMS Paths, from a persistent storage instead of in memoery cache of Sentry > service, to a Sentry consumer such as HDFS NameNode. It includes: > * Delta update retrieval logic from persistent storage. > * Propagation logic for consumer to get the delta update or a complete > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: SENTRY-1613.001-sentry-ha-redesign.patch > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the logic for propagating Sentry Permissions or Sentry representation of > HMS Paths, from a persistent storage instead of in memoery cache of Sentry > service, to a Sentry consumer such as HDFS NameNode. It includes: > * Delta update retrieval logic from persistent storage. > * Propagation logic for consumer to get the delta update or a complete > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1642) Integrate Sentry build with Error Prone
[
https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891736#comment-15891736
]
Hadoop QA commented on SENTRY-1642:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855565/SENTRY-1642.001.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2393/console
This message is automatically generated.
> Integrate Sentry build with Error Prone
> ---
>
> Key: SENTRY-1642
> URL: https://issues.apache.org/jira/browse/SENTRY-1642
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1642.001.patch
>
>
> Error Prone (http://errorprone.info/) is a nice tool to catch various Java
> bugs. We should integrate it with Sentry build and fix all issues discovered.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (SENTRY-1575) Backport SENTRY-1404 to Sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reassigned SENTRY-1575: --- Assignee: (was: Hao Hao) > Backport SENTRY-1404 to Sentry-ha-redesign branch > - > > Key: SENTRY-1575 > URL: https://issues.apache.org/jira/browse/SENTRY-1575 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1404.001-sentry-ha-redesign.patch > > > After Sentry-1499 which enables feature flag for Notification log. Need to > backport Sentry-1404 to make sure HDFS sync tests are passing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Open (was: Patch Available) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[
https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891730#comment-15891730
]
Hadoop QA commented on SENTRY-1613:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/1280/SENTRY-1613.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2390/console
This message is automatically generated.
> Add propagating logic for Perm/Path updates in Sentry service
> -
>
> Key: SENTRY-1613
> URL: https://issues.apache.org/jira/browse/SENTRY-1613
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Hao Hao
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1613.001-sentry-ha-redesign.patch
>
>
> Add the logic for propagating Sentry Permissions or Sentry representation of
> HMS Paths, from a persistent storage instead of in memoery cache of Sentry
> service, to a Sentry consumer such as HDFS NameNode. It includes:
> * Delta update retrieval logic from persistent storage.
> * Propagation logic for consumer to get the delta update or a complete
> snapshot.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Description: Add the logic for propagating Sentry Permissions or Sentry representation of HMS Paths, from a persistent storage instead of in memoery cache of Sentry service, to a Sentry consumer such as HDFS NameNode. It includes: * Delta update retrieval logic from persistent storage. * Propagation logic for consumer to get the delta update or a complete snapshot. was:Add the propagating logic for Perm/Path updates which stored in DB in Sentry service. This jira only supports the Path updates come from notification log, . > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the logic for propagating Sentry Permissions or Sentry representation of > HMS Paths, from a persistent storage instead of in memoery cache of Sentry > service, to a Sentry consumer such as HDFS NameNode. It includes: > * Delta update retrieval logic from persistent storage. > * Propagation logic for consumer to get the delta update or a complete > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: SENTRY-1642.001.patch > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: (was: SENTRY-1642.001.patch) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Patch Available (was: Open) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1642) Integrate Sentry build with Error Prone
[
https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891698#comment-15891698
]
Hadoop QA commented on SENTRY-1642:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/1284/SENTRY-1642.001.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2392/console
This message is automatically generated.
> Integrate Sentry build with Error Prone
> ---
>
> Key: SENTRY-1642
> URL: https://issues.apache.org/jira/browse/SENTRY-1642
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1642.001.patch
>
>
> Error Prone (http://errorprone.info/) is a nice tool to catch various Java
> bugs. We should integrate it with Sentry build and fix all issues discovered.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Patch Available (was: Open) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: SENTRY-1642.001.patch > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Open (was: Patch Available) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: (was: SENTRY-1642.001.patch) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1642) Integrate Sentry build with Error Prone
[
https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891683#comment-15891683
]
Hadoop QA commented on SENTRY-1642:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/1281/SENTRY-1642.001.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2391/console
This message is automatically generated.
> Integrate Sentry build with Error Prone
> ---
>
> Key: SENTRY-1642
> URL: https://issues.apache.org/jira/browse/SENTRY-1642
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0, sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1642.001.patch
>
>
> Error Prone (http://errorprone.info/) is a nice tool to catch various Java
> bugs. We should integrate it with Sentry build and fix all issues discovered.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Attachment: SENTRY-1642.001.patch > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1642) Integrate Sentry build with Error Prone
[ https://issues.apache.org/jira/browse/SENTRY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1642: --- Status: Patch Available (was: In Progress) > Integrate Sentry build with Error Prone > --- > > Key: SENTRY-1642 > URL: https://issues.apache.org/jira/browse/SENTRY-1642 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0, sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Attachments: SENTRY-1642.001.patch > > > Error Prone (http://errorprone.info/) is a nice tool to catch various Java > bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SENTRY-1642) Integrate Sentry build with Error Prone
Alexander Kolbasov created SENTRY-1642: -- Summary: Integrate Sentry build with Error Prone Key: SENTRY-1642 URL: https://issues.apache.org/jira/browse/SENTRY-1642 Project: Sentry Issue Type: Improvement Components: Sentry Affects Versions: 1.8.0, sentry-ha-redesign Reporter: Alexander Kolbasov Assignee: Alexander Kolbasov Error Prone (http://errorprone.info/) is a nice tool to catch various Java bugs. We should integrate it with Sentry build and fix all issues discovered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: SENTRY-1613.001-sentry-ha-redesign.patch > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1613.001-sentry-ha-redesign.patch > > > Add the propagating logic for Perm/Path updates which stored in DB in Sentry > service. This jira only supports the Path updates come from notification log, > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1613) Add propagating logic for Perm/Path updates in Sentry service
[ https://issues.apache.org/jira/browse/SENTRY-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1613: Attachment: (was: SENTRY-1613.001-sentry-ha-redesign.patch) > Add propagating logic for Perm/Path updates in Sentry service > - > > Key: SENTRY-1613 > URL: https://issues.apache.org/jira/browse/SENTRY-1613 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > > Add the propagating logic for Perm/Path updates which stored in DB in Sentry > service. This jira only supports the Path updates come from notification log, > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1601) Implement HMS Notification barrier on the server side
[
https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891628#comment-15891628
]
Hadoop QA commented on SENTRY-1601:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855534/SENTRY-1601.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2389/console
This message is automatically generated.
> Implement HMS Notification barrier on the server side
> -
>
> Key: SENTRY-1601
> URL: https://issues.apache.org/jira/browse/SENTRY-1601
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1601.001-sentry-ha-redesign.patch
>
>
> When Hive performs operations involving notifications (e.g. drops a table) we
> need to wait until the operation is processed by Sentry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1566) Make full Perm/Path snapshot available for NN plugin
[
https://issues.apache.org/jira/browse/SENTRY-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891557#comment-15891557
]
Hadoop QA commented on SENTRY-1566:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855522/SENTRY-1566.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2388/console
This message is automatically generated.
> Make full Perm/Path snapshot available for NN plugin
>
>
> Key: SENTRY-1566
> URL: https://issues.apache.org/jira/browse/SENTRY-1566
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Reporter: Hao Hao
>Assignee: Hao Hao
> Labels: hdfs-sync
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1566.001-sentry-ha-redesign.patch,
> SENTRY-1566.002-sentry-ha-redesign.patch
>
>
> Read full permission and path snapshot from SentryDB and make the update
> available for NN plugin upon requests. In detail:
> * Added Path/PermissionImage classes to represent corresponding
> Path/Permission snapshot read from DB.
> * Refactor full snapshot retriever APIs in SentryStore to become a single
> transaction to ensure snapshot consistency.
> * Added Path/PermissionImageRetriever classes to retrieve
> Path/PermissionImage from DB and convert to corresponding
> Path/PermissionUpdate, which later would be consumed by NN plugin.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Status: Patch Available (was: Open) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Attachment: SENTRY-1601.001-sentry-ha-redesign.patch Fixed broken TestHMSFollower. > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Status: Open (was: Patch Available) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Attachment: (was: SENTRY-1601.001-sentry-ha-redesign.patch) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1566) Make full Perm/Path snapshot available for NN plugin
[ https://issues.apache.org/jira/browse/SENTRY-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1566: Attachment: SENTRY-1566.002-sentry-ha-redesign.patch > Make full Perm/Path snapshot available for NN plugin > > > Key: SENTRY-1566 > URL: https://issues.apache.org/jira/browse/SENTRY-1566 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: Hao Hao > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1566.001-sentry-ha-redesign.patch, > SENTRY-1566.002-sentry-ha-redesign.patch > > > Read full permission and path snapshot from SentryDB and make the update > available for NN plugin upon requests. In detail: > * Added Path/PermissionImage classes to represent corresponding > Path/Permission snapshot read from DB. > * Refactor full snapshot retriever APIs in SentryStore to become a single > transaction to ensure snapshot consistency. > * Added Path/PermissionImageRetriever classes to retrieve > Path/PermissionImage from DB and convert to corresponding > Path/PermissionUpdate, which later would be consumed by NN plugin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SENTRY-1617) Fetch Hive Paths point-in-time full snapshot during Sentry startup
[ https://issues.apache.org/jira/browse/SENTRY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved SENTRY-1617. - Resolution: Fixed > Fetch Hive Paths point-in-time full snapshot during Sentry startup > --- > > Key: SENTRY-1617 > URL: https://issues.apache.org/jira/browse/SENTRY-1617 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > > A Uber jira to capture all tasks for fetching a point-in-time full snapshot > during Sentry startup. The flow is described as below: > * Try to get a HMSPath full snapshot by reading from DB. > * If there is no such snapshot exists inside DB, it reads a point-in-time > full HMSPaths snapshot from HMS and persist it into DB. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Resolution: Fixed Status: Resolved (was: Patch Available) > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch, > SENTRY-1612.002-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891473#comment-15891473 ] Hao Hao commented on SENTRY-1612: - Transferring +1 from RB. > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch, > SENTRY-1612.002-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1601) Implement HMS Notification barrier on the server side
[
https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891465#comment-15891465
]
Hadoop QA commented on SENTRY-1601:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855511/SENTRY-1601.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to 6 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.service.thrift.TestHMSFollower
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2387/console
This message is automatically generated.
> Implement HMS Notification barrier on the server side
> -
>
> Key: SENTRY-1601
> URL: https://issues.apache.org/jira/browse/SENTRY-1601
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1601.001-sentry-ha-redesign.patch
>
>
> When Hive performs operations involving notifications (e.g. drops a table) we
> need to wait until the operation is processed by Sentry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Status: Patch Available (was: Open) Addressed code review comments > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Attachment: SENTRY-1601.001-sentry-ha-redesign.patch > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Attachment: (was: SENTRY-1601.001-sentry-ha-redesign.patch) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Status: Open (was: Patch Available) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[
https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891427#comment-15891427
]
Hadoop QA commented on SENTRY-1612:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855496/SENTRY-1612.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2386/console
This message is automatically generated.
> HMSFollower should persist full HMS snapshot into SentryDB if there is not
> one.
> ---
>
> Key: SENTRY-1612
> URL: https://issues.apache.org/jira/browse/SENTRY-1612
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Hao Hao
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1612.001-sentry-ha-redesign.patch,
> SENTRY-1612.002-sentry-ha-redesign.patch
>
>
> During Sentry service start, after reads a point-in-time full HMSPaths
> snapshot from HMS and record the corresponding notification ID, HMSFollwer
> should persist it into Sentry DB.
> Otherwise if a full snapshot is stored in DB, read the corresponding
> currentEventID from sentry store.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[
https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891388#comment-15891388
]
Hadoop QA commented on SENTRY-1612:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855490/SENTRY-1612.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2385/console
This message is automatically generated.
> HMSFollower should persist full HMS snapshot into SentryDB if there is not
> one.
> ---
>
> Key: SENTRY-1612
> URL: https://issues.apache.org/jira/browse/SENTRY-1612
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Hao Hao
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1612.001-sentry-ha-redesign.patch,
> SENTRY-1612.002-sentry-ha-redesign.patch
>
>
> During Sentry service start, after reads a point-in-time full HMSPaths
> snapshot from HMS and record the corresponding notification ID, HMSFollwer
> should persist it into Sentry DB.
> Otherwise if a full snapshot is stored in DB, read the corresponding
> currentEventID from sentry store.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1569) Upgrading SQL scripts for persist Perm/Path change
[ https://issues.apache.org/jira/browse/SENTRY-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1569: Attachment: (was: SENTRY-1569.004-sentry-ha-redesign.patch) > Upgrading SQL scripts for persist Perm/Path change > -- > > Key: SENTRY-1569 > URL: https://issues.apache.org/jira/browse/SENTRY-1569 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: kalyan kumar kalvagadda > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1569.001-sentry-ha-redesign.patch, > SENTRY-1569.003-sentry-ha-redesign.patch > > > Upgrading SQL script for Sentry permission and HMS path change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Attachment: SENTRY-1612.002-sentry-ha-redesign.patch > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch, > SENTRY-1612.002-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Attachment: (was: SENTRY-1612.002-sentry-ha-redesign.patch) > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Attachment: SENTRY-1612.002-sentry-ha-redesign.patch > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch, > SENTRY-1612.002-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1569) Upgrading SQL scripts for persist Perm/Path change
[ https://issues.apache.org/jira/browse/SENTRY-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1569: Attachment: SENTRY-1569.004-sentry-ha-redesign.patch > Upgrading SQL scripts for persist Perm/Path change > -- > > Key: SENTRY-1569 > URL: https://issues.apache.org/jira/browse/SENTRY-1569 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: kalyan kumar kalvagadda > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1569.001-sentry-ha-redesign.patch, > SENTRY-1569.003-sentry-ha-redesign.patch, > SENTRY-1569.004-sentry-ha-redesign.patch > > > Upgrading SQL script for Sentry permission and HMS path change. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1638) Update SQL script of MSentryPathChange table to add a column for notification ID
[
https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891265#comment-15891265
]
Hadoop QA commented on SENTRY-1638:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855461/SENTRY-1638.01-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2383/console
This message is automatically generated.
> Update SQL script of MSentryPathChange table to add a column for notification
> ID
>
>
> Key: SENTRY-1638
> URL: https://issues.apache.org/jira/browse/SENTRY-1638
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Lei (Eddy) Xu
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1638.01-sentry-ha-redesign.patch,
> SENTRY-1638.02-sentry-ha-redesign.patch
>
>
> For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs
> to be updated to add a column for notification ID to support the change in
> SENTRY-1448.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update SQL script of MSentryPathChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1638: Description: For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs to be updated to add a column for notification ID to support the change in SENTRY-1448. (was: For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs to be updated to add a column for notification ID to support the change in SENTRY_1448.) > Update SQL script of MSentryPathChange table to add a column for notification > ID > > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs > to be updated to add a column for notification ID to support the change in > SENTRY-1448. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update SQL script of MSentryPathChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1638: Description: For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs to be updated to add a column for notification ID to support the change in SENTRY_1448. (was: For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs to be updated to add a column for notification ID.) > Update SQL script of MSentryPathChange table to add a column for notification > ID > > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs > to be updated to add a column for notification ID to support the change in > SENTRY_1448. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update SQL script of MSentryPathChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1638: Description: For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs to be updated to add a column for notification ID. (was: For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to add a column for notification ID.) > Update SQL script of MSentryPathChange table to add a column for notification > ID > > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, the SQL Script of MSentryPathChange table needs > to be updated to add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update SQL script of MSentryPathChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1638: Summary: Update SQL script of MSentryPathChange table to add a column for notification ID (was: Update MSentryPermChange table to add a column for notification ID) > Update SQL script of MSentryPathChange table to add a column for notification > ID > > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891239#comment-15891239 ] Alexander Kolbasov commented on SENTRY-1638: The commit was reverted. [~hahao] found some issues during review. > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reopened SENTRY-1638: > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SENTRY-1641) Cleanup creation of SentryStore and HMSFollower
[ https://issues.apache.org/jira/browse/SENTRY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu resolved SENTRY-1641. --- Resolution: Duplicate Yea, it has already been fixed in SENTRY-1637. Thanks for reporting this, [~akolb] > Cleanup creation of SentryStore and HMSFollower > --- > > Key: SENTRY-1641 > URL: https://issues.apache.org/jira/browse/SENTRY-1641 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Reporter: Alexander Kolbasov >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > > Currently HMSFollower is created in the constructor of SentryService and it > creates SentryStore for itself. > Instead the SentryService should create SentryStore and HMSFollower later in > the run() method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1638: --- Resolution: Fixed Fix Version/s: sentry-ha-redesign Status: Resolved (was: Patch Available) [~Lei Xu] Thank you for your contribution! > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[
https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891224#comment-15891224
]
Hadoop QA commented on SENTRY-1638:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855467/SENTRY-1638.02-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to 5 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2384/console
This message is automatically generated.
> Update MSentryPermChange table to add a column for notification ID
> --
>
> Key: SENTRY-1638
> URL: https://issues.apache.org/jira/browse/SENTRY-1638
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Lei (Eddy) Xu
> Attachments: SENTRY-1638.01-sentry-ha-redesign.patch,
> SENTRY-1638.02-sentry-ha-redesign.patch
>
>
> For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to
> add a column for notification ID.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated SENTRY-1638: -- Attachment: SENTRY-1638.02-sentry-ha-redesign.patch > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch, > SENTRY-1638.02-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated SENTRY-1638: -- Fix Version/s: (was: sentry-ha-redesign) Affects Version/s: sentry-ha-redesign Status: Patch Available (was: Open) > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update MSentryPermChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated SENTRY-1638: -- Summary: Update MSentryPermChange table to add a column for notification ID (was: Update MSentryPathChange table to add a column for notification ID) > Update MSentryPermChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1638) Update MSentryPathChange table to add a column for notification ID
[ https://issues.apache.org/jira/browse/SENTRY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated SENTRY-1638: -- Attachment: SENTRY-1638.01-sentry-ha-redesign.patch Update the patch which is similar to SENTRY-1448. > Update MSentryPathChange table to add a column for notification ID > -- > > Key: SENTRY-1638 > URL: https://issues.apache.org/jira/browse/SENTRY-1638 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1638.01-sentry-ha-redesign.patch > > > For follow up of SENTRY-1448, MSentryPathChange table needs to be updated to > add a column for notification ID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[
https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891100#comment-15891100
]
Hadoop QA commented on SENTRY-1612:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855443/SENTRY-1612.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2381/console
This message is automatically generated.
> HMSFollower should persist full HMS snapshot into SentryDB if there is not
> one.
> ---
>
> Key: SENTRY-1612
> URL: https://issues.apache.org/jira/browse/SENTRY-1612
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Hao Hao
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1612.001-sentry-ha-redesign.patch
>
>
> During Sentry service start, after reads a point-in-time full HMSPaths
> snapshot from HMS and record the corresponding notification ID, HMSFollwer
> should persist it into Sentry DB.
> Otherwise if a full snapshot is stored in DB, read the corresponding
> currentEventID from sentry store.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Status: Patch Available (was: In Progress) > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SENTRY-1567) Refactor propagating logic for Perm/Path delta to NN plugin
[ https://issues.apache.org/jira/browse/SENTRY-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved SENTRY-1567. - Resolution: Won't Fix > Refactor propagating logic for Perm/Path delta to NN plugin > --- > > Key: SENTRY-1567 > URL: https://issues.apache.org/jira/browse/SENTRY-1567 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > > Refactor the propagating logic for Perm/Path delta to NN plugin to remove > caching logic. Instead read Perm/Path delta from SentryDB. This jira was > created to captures supports both for current HMS events flow(which comes > from HMS plugin) and Hive notification log events flow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (SENTRY-1601) Implement HMS Notification barrier on the server side
[
https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891064#comment-15891064
]
Alexander Kolbasov edited comment on SENTRY-1601 at 3/1/17 9:26 PM:
The patch addresses Sentry Server side functionality only. To test this end to
end we still need HMS support.
The patch includes the following:
* {{CounterWait}} class that provides core functionality for synchronization
between waiters and processor {{HMSFollower}} and a unit test for it.
* {{SentryStore}} plumbing
* Implementation on the Thrift side in {{SentryPolicyStoreProcessor}}
was (Author: akolb):
The patch addresses Sentry Server side functionality only. To test this end to
end we still need HMS support.
The patch includes the following:
* {code}CounterWait{code} class that provides core functionality for
synchronization between waiters and processor (HMSFollower) and a unit test for
it.
* {code{SentryStore{code} plumbing
* Implementation on the Thrift side in {code}SentryPolicyStoreProcessor{code}
> Implement HMS Notification barrier on the server side
> -
>
> Key: SENTRY-1601
> URL: https://issues.apache.org/jira/browse/SENTRY-1601
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1601.001-sentry-ha-redesign.patch
>
>
> When Hive performs operations involving notifications (e.g. drops a table) we
> need to wait until the operation is processed by Sentry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1601) Implement HMS Notification barrier on the server side
[
https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891064#comment-15891064
]
Alexander Kolbasov commented on SENTRY-1601:
The patch addresses Sentry Server side functionality only. To test this end to
end we still need HMS support.
The patch includes the following:
* {code}CounterWait{code} class that provides core functionality for
synchronization between waiters and processor (HMSFollower) and a unit test for
it.
* {code{SentryStore{code} plumbing
* Implementation on the Thrift side in {code}SentryPolicyStoreProcessor{code}
> Implement HMS Notification barrier on the server side
> -
>
> Key: SENTRY-1601
> URL: https://issues.apache.org/jira/browse/SENTRY-1601
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1601.001-sentry-ha-redesign.patch
>
>
> When Hive performs operations involving notifications (e.g. drops a table) we
> need to wait until the operation is processed by Sentry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1601) Implement HMS Notification barrier on the server side
[ https://issues.apache.org/jira/browse/SENTRY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1601: --- Attachment: SENTRY-1601.001-sentry-ha-redesign.patch > Implement HMS Notification barrier on the server side > - > > Key: SENTRY-1601 > URL: https://issues.apache.org/jira/browse/SENTRY-1601 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1601.001-sentry-ha-redesign.patch > > > When Hive performs operations involving notifications (e.g. drops a table) we > need to wait until the operation is processed by Sentry. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Attachment: SENTRY-1612.001-sentry-ha-redesign.patch > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1612.001-sentry-ha-redesign.patch > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1612) HMSFollower should persist full HMS snapshot into SentryDB if there is not one.
[ https://issues.apache.org/jira/browse/SENTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1612: Attachment: (was: SENTRY-1612.001-sentry-ha-redesign.patch) > HMSFollower should persist full HMS snapshot into SentryDB if there is not > one. > --- > > Key: SENTRY-1612 > URL: https://issues.apache.org/jira/browse/SENTRY-1612 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Hao Hao > Fix For: sentry-ha-redesign > > > During Sentry service start, after reads a point-in-time full HMSPaths > snapshot from HMS and record the corresponding notification ID, HMSFollwer > should persist it into Sentry DB. > Otherwise if a full snapshot is stored in DB, read the corresponding > currentEventID from sentry store. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
