[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 > > Attachments: hms-sentry.png, hms-sentry-sync.png, > 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 > > Attachments: hms-sentry.png, hms-sentry-sync.png, > 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) > 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: hms-sentry.png, hms-sentry-sync.png, > 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=15893561#comment-15893561
]
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/2399/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: hms-sentry.png, hms-sentry-sync.png,
> 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-1644) After alter location of Hive table with partitions, ACLs still remain the same for the old partition paths
[ https://issues.apache.org/jira/browse/SENTRY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1644: --- Affects Version/s: sentry-ha-redesign 1.8.0 > After alter location of Hive table with partitions, ACLs still remain the > same for the old partition paths > > > Key: SENTRY-1644 > URL: https://issues.apache.org/jira/browse/SENTRY-1644 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 1.7.0, 1.8.0, sentry-ha-redesign >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > > After rename Hive table with partitions, ACLs still remain the same for the > old partition paths. > It can be reproducible by: > * Create a table with partitions. > * Alter the table location > * Check the ACLs on the partitions old path, it will remain the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (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 ] kalyan kumar kalvagadda reassigned SENTRY-1638: --- Assignee: kalyan kumar kalvagadda (was: Lei (Eddy) Xu) > 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: kalyan kumar kalvagadda > 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] [Assigned] (SENTRY-1644) After alter location of Hive table with partitions, ACLs still remain the same for the old partition paths
[ https://issues.apache.org/jira/browse/SENTRY-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu reassigned SENTRY-1644: - Assignee: Lei (Eddy) Xu > After alter location of Hive table with partitions, ACLs still remain the > same for the old partition paths > > > Key: SENTRY-1644 > URL: https://issues.apache.org/jira/browse/SENTRY-1644 > Project: Sentry > Issue Type: Bug > Components: Hdfs Plugin >Affects Versions: 1.7.0 >Reporter: Hao Hao >Assignee: Lei (Eddy) Xu > > After rename Hive table with partitions, ACLs still remain the same for the > old partition paths. > It can be reproducible by: > * Create a table with partitions. > * Alter the table location > * Check the ACLs on the partitions old path, it will remain the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei (Eddy) Xu reassigned SENTRY-1643:
-
Assignee: Lei (Eddy) Xu
> 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
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Lei (Eddy) Xu
> Fix For: sentry-ha-redesign
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat}
>
>
> {noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
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=15893201#comment-15893201
]
Hadoop QA commented on SENTRY-1566:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855701/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/2398/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] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893199#comment-15893199
]
Hao Hao commented on SENTRY-1643:
-
[~akolb] Updated the description with more detail, please let me know if this
is sufficient.
> 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
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
> Fix For: sentry-ha-redesign
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat}
>
>
> {noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated SENTRY-1643:
Description:
In MSentryPermChange/MSentryPathChange table, the changeID field is
auto-increment.
{noformat}
{noformat}
However, found through the integration unit test TestHDFSIntegration, the value
does not seem to be correctly auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
was:
In MSentryPermChange/MSentryPathChange table, the changeID field is
auto-increment.
{noformat}
{noformat}
However, found through the integration unit test TestHDFSIntegration, the value
does not seem to be correctly auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
> 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
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
> Fix For: sentry-ha-redesign
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat}
>
>
> {noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated SENTRY-1643:
Description:
In MSentryPermChange/MSentryPathChange table, the changeID field is
auto-increment.
{noformat}
{noformat}
However, found through the integration unit test TestHDFSIntegration, the value
does not seem to be correctly auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
was:
In MSentryPermChange/MSentryPathChange table, the changeID field is
auto-increment.
{noformat}
{noformat}
However, found through the integration unit test TestHDFSIntegration, the value
does not seem to be correctly auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
> 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
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
> Fix For: sentry-ha-redesign
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat}
>
>
> {noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated SENTRY-1643:
Description:
In MSentryPermChange/MSentryPathChange table, the changeID field is
auto-increment.
{noformat}
{noformat}
However, found through the integration unit test TestHDFSIntegration, the value
does not seem to be correctly auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
was:
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 auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
> 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
> Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
> Fix For: sentry-ha-redesign
>
>
> In MSentryPermChange/MSentryPathChange table, the changeID field is
> auto-increment.
> {noformat} value-strategy="increment">
>
>{noformat}
> However, found through the integration unit test TestHDFSIntegration, the
> value does not seem to be correctly auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[
https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Hao updated SENTRY-1643:
Description:
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 auto increased. e.g Instead of increasing by one
for each new entry, it increased by some unexpected number.
was: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.
> 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
> Components: Hdfs Plugin
>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 auto increased. e.g Instead of increasing
> by one for each new entry, it increased by some unexpected number.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone
[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893182#comment-15893182 ] Alexander Kolbasov commented on SENTRY-1643: Can you clarify what is the problem? > 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 > Components: Hdfs Plugin >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-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] [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: (was: 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 > > > 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] [Created] (SENTRY-1644) After alter location of Hive table with partitions, ACLs still remain the same for the old partition paths
Hao Hao created SENTRY-1644: --- Summary: After alter location of Hive table with partitions, ACLs still remain the same for the old partition paths Key: SENTRY-1644 URL: https://issues.apache.org/jira/browse/SENTRY-1644 Project: Sentry Issue Type: Bug Components: Hdfs Plugin Affects Versions: 1.7.0 Reporter: Hao Hao After rename Hive table with partitions, ACLs still remain the same for the old partition paths. It can be reproducible by: * Create a table with partitions. * Alter the table location * Check the ACLs on the partitions old path, it will remain the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (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 ] Lei (Eddy) Xu resolved SENTRY-1638. --- Resolution: Duplicate Kalyan generously offer to fix SQL script in SENTRY-1569. > 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] [Commented] (SENTRY-1548) Setting GrantOption to UNSET upsets Sentry
[
https://issues.apache.org/jira/browse/SENTRY-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892713#comment-15892713
]
Hadoop QA commented on SENTRY-1548:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855655/SENTRY-1548.007.patch
against master.
{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/2397/console
This message is automatically generated.
> Setting GrantOption to UNSET upsets Sentry
> --
>
> Key: SENTRY-1548
> URL: https://issues.apache.org/jira/browse/SENTRY-1548
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Reporter: Alexander Kolbasov
>Assignee: kalyan kumar kalvagadda
>Priority: Minor
> Labels: bite-sized
> Attachments: SENTRY-1548.001.patch, SENTRY-1548.002.patch,
> SENTRY-1548.003.patch, SENTRY-1548.005.patch, SENTRY-1548.006.patch,
> SENTRY-1548.007.patch
>
>
> If we send a Thrift request to sentry (using regular api) with GrantOption
> set to UNSET (-1) we get the following error:
> {code}
> TransactionManager.executeTransactionWithRetry(TransactionManager.java:102)]
> The transaction has reac
> hed max retry number, will not retry again.
> javax.jdo.JDODataStoreException: Insert of object
> "org.apache.sentry.provider.db.service.model.MSentryPrivilege@6bbfd4c9" using
> statement "INSERT INTO `SENTRY_DB_PRIVILEGE`
> (`DB_PRIVILEGE_ID`,`SERVER_NAME`,`WITH_GRANT_OPTION`,`CREATE_TIME`,`TABLE_NAME`,`URI`,`ACTION`,`COLUMN_NAME`,`DB_NAME`,`PRIVILEGE_SCOPE`)
> VALUES (?,?,?,?,?,?,?,?,?,?)" failed : Column 'WITH_GRANT_OPTION' cannot be
> null
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:451)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:732)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:752)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.alterSentryRoleGrantPrivilegeCore(SentryStore.java:438)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.access$500(SentryStore.java:95)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore$8.execute(SentryStore.java:374)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransaction(TransactionManager.java:72)
> at
> org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransactionWithRetry(TransactionManager.java:93)
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.alterSentryRoleGrantPrivileges(SentryStore.java:367)
> at
> org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor.alter_sentry_role_grant_privilege(SentryPolicyStoreProcessor.java:280)
> at
> org.apache.sentry.provider.db.service.thrift.SentryPolicyService$Processor$alter_sentry_role_grant_privilege.getResult(SentryPolicyService.java:1237)
> at
> org.apache.sentry.provider.db.service.thrift.SentryPolicyService$Processor$alter_sentry_role_grant_privilege.getResult(SentryPolicyService.java:1222)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.sentry.provider.db.service.thrift.SentryProcessorWrapper.process(SentryProcessorWrapper.java:35)
> at
> org.apache.thrift.TMultiplexedProcessor.process(TMultiplexedProcessor.java:123)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> NestedThrowablesStackTrace:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Column 'WITH_GRANT_OPTION' cannot be null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
> at com.mysql.jdbc.Util.getInstance(Util.java:387)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934)
> at
[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=15891883#comment-15891883
]
Hadoop QA commented on SENTRY-1613:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12855569/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/2396/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)
