[jira] [Updated] (SENTRY-1536) Refactor SentryStore transaction management to allow for extra transactions for a single permission update
[ https://issues.apache.org/jira/browse/SENTRY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1536: Attachment: SENTRY-1536.003-sentry-ha-redesign.patch > Refactor SentryStore transaction management to allow for extra transactions > for a single permission update > -- > > Key: SENTRY-1536 > URL: https://issues.apache.org/jira/browse/SENTRY-1536 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Hao Hao > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1536.001-sentry-ha-redesign.patch, > SENTRY-1536.002-sentry-ha-redesign.patch, > SENTRY-1536.003-sentry-ha-redesign.patch > > > To persist single permission change, it needs to combine multiple things in a > single transaction: > * Doing the actual operation (priv change) > * Updating notification ID. > It is important to do this in a single transaction to guarantee that > notificationID handling is atomic. Current code structure doesn't allow for > that. > So we need to pass extra transaction code to SentryStore functions or figure > out a generic way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1536) Refactor SentryStore transaction management to allow for extra transactions for a single permission update
[ https://issues.apache.org/jira/browse/SENTRY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1536: Attachment: (was: SENTRY-1536.003-sentry-ha-redesign.patch) > Refactor SentryStore transaction management to allow for extra transactions > for a single permission update > -- > > Key: SENTRY-1536 > URL: https://issues.apache.org/jira/browse/SENTRY-1536 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Hao Hao > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1536.001-sentry-ha-redesign.patch, > SENTRY-1536.002-sentry-ha-redesign.patch > > > To persist single permission change, it needs to combine multiple things in a > single transaction: > * Doing the actual operation (priv change) > * Updating notification ID. > It is important to do this in a single transaction to guarantee that > notificationID handling is atomic. Current code structure doesn't allow for > that. > So we need to pass extra transaction code to SentryStore functions or figure > out a generic way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=15840795#comment-15840795
]
Hadoop QA commented on SENTRY-1566:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12849609/SENTRY-1566.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{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/2283/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
>
>
> 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.4#6332)
[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=15840796#comment-15840796
]
Hadoop QA commented on SENTRY-1612:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12849618/SENTRY-1612.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{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/2284/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.4#6332)
[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: Status: Patch Available (was: Open) > 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.4#6332)
[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.4#6332)
[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 > > 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.4#6332)
[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.001-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.4#6332)
[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.001-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 > > > 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.4#6332)
[jira] [Commented] (SENTRY-1536) Refactor SentryStore transaction management to allow for extra transactions for a single permission update
[
https://issues.apache.org/jira/browse/SENTRY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840672#comment-15840672
]
Hadoop QA commented on SENTRY-1536:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12849599/SENTRY-1536.003-sentry-ha-redesign.patch
against sentry-ha-redesign.
{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/2282/console
This message is automatically generated.
> Refactor SentryStore transaction management to allow for extra transactions
> for a single permission update
> --
>
> Key: SENTRY-1536
> URL: https://issues.apache.org/jira/browse/SENTRY-1536
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Hao Hao
> Labels: hdfs-sync
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1536.001-sentry-ha-redesign.patch,
> SENTRY-1536.002-sentry-ha-redesign.patch,
> SENTRY-1536.003-sentry-ha-redesign.patch
>
>
> To persist single permission change, it needs to combine multiple things in a
> single transaction:
> * Doing the actual operation (priv change)
> * Updating notification ID.
> It is important to do this in a single transaction to guarantee that
> notificationID handling is atomic. Current code structure doesn't allow for
> that.
> So we need to pass extra transaction code to SentryStore functions or figure
> out a generic way to do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SENTRY-1536) Refactor SentryStore transaction management to allow for extra transactions for a single permission update
[ https://issues.apache.org/jira/browse/SENTRY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1536: Attachment: SENTRY-1536.003-sentry-ha-redesign.patch > Refactor SentryStore transaction management to allow for extra transactions > for a single permission update > -- > > Key: SENTRY-1536 > URL: https://issues.apache.org/jira/browse/SENTRY-1536 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Hao Hao > Labels: hdfs-sync > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1536.001-sentry-ha-redesign.patch, > SENTRY-1536.002-sentry-ha-redesign.patch, > SENTRY-1536.003-sentry-ha-redesign.patch > > > To persist single permission change, it needs to combine multiple things in a > single transaction: > * Doing the actual operation (priv change) > * Updating notification ID. > It is important to do this in a single transaction to guarantee that > notificationID handling is atomic. Current code structure doesn't allow for > that. > So we need to pass extra transaction code to SentryStore functions or figure > out a generic way to do this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1602) Code cleanup for Sentry JSON message factory for hive notifications
[ https://issues.apache.org/jira/browse/SENTRY-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840601#comment-15840601 ] Nachiket Vaidya commented on SENTRY-1602: - [~akolb] and [~hahao]: Added review link. Thank you. > Code cleanup for Sentry JSON message factory for hive notifications > --- > > Key: SENTRY-1602 > URL: https://issues.apache.org/jira/browse/SENTRY-1602 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Nachiket Vaidya >Assignee: Nachiket Vaidya > Labels: patch-available > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1602.0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SENTRY-1604) Sentry JSON message factory: Need more information in alter partition event
[
https://issues.apache.org/jira/browse/SENTRY-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840600#comment-15840600
]
Nachiket Vaidya commented on SENTRY-1604:
-
[~akolb] and [~hahao]: Added review link. Thank you.
> Sentry JSON message factory: Need more information in alter partition event
> ---
>
> Key: SENTRY-1604
> URL: https://issues.apache.org/jira/browse/SENTRY-1604
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Nachiket Vaidya
>Assignee: Nachiket Vaidya
> Labels: patch-available
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1604.0.patch
>
>
> When the query is:
> {noformat}
> alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to
> partition (bbb = 'r1', aaa='r2', ccc='r3')
> {noformat}
> Update:
> {noformat}
> | 8375 | 8371 | 1469487373 | ALTER_PARTITION | test_a
> |
> test_b|
> {"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111",
> "222", "333"},"eventType":"ALTER_PARTITION"}
>
> {noformat}
> We need to provide more info in notification entry.
> Currently, message factory for alter partition does not store new partition
> values. It just stores old values. For alter partition with partition change,
> we need both values.
> In this fix, sentry message factory stores also new partition values in alter
> partition message in addition to old values. Added unit test cases for the
> same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SENTRY-1604) Sentry JSON message factory: Need more information in alter partition event
[
https://issues.apache.org/jira/browse/SENTRY-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840526#comment-15840526
]
Hao Hao commented on SENTRY-1604:
-
[~vaidyand] would you mind to add a RB link for this? Thanks!
> Sentry JSON message factory: Need more information in alter partition event
> ---
>
> Key: SENTRY-1604
> URL: https://issues.apache.org/jira/browse/SENTRY-1604
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Nachiket Vaidya
>Assignee: Nachiket Vaidya
> Labels: patch-available
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1604.0.patch
>
>
> When the query is:
> {noformat}
> alter table test_b partition (bbb = '111', aaa='222', ccc='333') rename to
> partition (bbb = 'r1', aaa='r2', ccc='r3')
> {noformat}
> Update:
> {noformat}
> | 8375 | 8371 | 1469487373 | ALTER_PARTITION | test_a
> |
> test_b|
> {"timestamp":1469487373,"servicePrincipal":"","server":"","table":"test_b","db":"test_a","values":{"111",
> "222", "333"},"eventType":"ALTER_PARTITION"}
>
> {noformat}
> We need to provide more info in notification entry.
> Currently, message factory for alter partition does not store new partition
> values. It just stores old values. For alter partition with partition change,
> we need both values.
> In this fix, sentry message factory stores also new partition values in alter
> partition message in addition to old values. Added unit test cases for the
> same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SENTRY-1580) Provide pooled client connection model with HA
[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840300#comment-15840300 ] Alexander Kolbasov commented on SENTRY-1580: Kalyan is working on failover JIRAs. > Provide pooled client connection model with HA > -- > > Key: SENTRY-1580 > URL: https://issues.apache.org/jira/browse/SENTRY-1580 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda > Fix For: sentry-ha-redesign > > > SENTRY-1477 provided a simple connection retry model which is incompatible > with the object pool. I think that we can combine the pool model in case of > multiple connections by using GenericKeyedObjectPool using server address as > a key. When we suspect a disconnect we can clear the whole sub-pool using > clear(key). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SENTRY-1580) Provide pooled client connection model with HA
[ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1580: --- Assignee: kalyan kumar kalvagadda (was: Vamsee Yarlagadda) > Provide pooled client connection model with HA > -- > > Key: SENTRY-1580 > URL: https://issues.apache.org/jira/browse/SENTRY-1580 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda > Fix For: sentry-ha-redesign > > > SENTRY-1477 provided a simple connection retry model which is incompatible > with the object pool. I think that we can combine the pool model in case of > multiple connections by using GenericKeyedObjectPool using server address as > a key. When we suspect a disconnect we can clear the whole sub-pool using > clear(key). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SENTRY-1615) SentryStore should not allocate empty objects that are immediately returned
Alexander Kolbasov created SENTRY-1615: -- Summary: SentryStore should not allocate empty objects that are immediately returned Key: SENTRY-1615 URL: https://issues.apache.org/jira/browse/SENTRY-1615 Project: Sentry Issue Type: Improvement Components: Sentry Affects Versions: 1.8.0, sentry-ha-redesign Reporter: Alexander Kolbasov Assignee: Alexander Kolbasov Priority: Minor There are a few places where SentryStore returns some empty lists or sets - it shouldn't allocate them but return pre-made Collection objects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-1614) DB Schme Init is failing on sentry HA branch
[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839700#comment-15839700
]
kalyan kumar kalvagadda edited comment on SENTRY-1614 at 1/26/17 1:56 PM:
--
*Here is the analysis done:*
one of the tables added as part of sentry HA, MAUTHZPATHSMAPPING_PATHS had a
column of size VARCHAR(4000) as part of the primary key. This is the root cause
for the issue.
{noformat}
CREATE TABLE `MAUTHZPATHSMAPPING_PATHS`
(
`AUTHZ_OBJ_ID_OID` BIGINT NOT NULL,
`PATHS` VARCHAR(500) BINARY NOT NULL,
CONSTRAINT `MAUTHZPATHSMAPPING_PATHS_PK` PRIMARY KEY
(`AUTHZ_OBJ_ID_OID`,`PATHS`)
) ENGINE=INNODB;
{noformat}
We need to evaluate if we need PATHS part of primary key and take appropriate
direction.
was (Author: kkalyan):
*Here is the analysis done:*
one of the tables added as part of sentry HA, MAUTHZPATHSMAPPING_PATHS had a
column of size VARCHAR(4000) as part of the primary key. This is the reason.
{noformat}
CREATE TABLE `MAUTHZPATHSMAPPING_PATHS`
(
`AUTHZ_OBJ_ID_OID` BIGINT NOT NULL,
`PATHS` VARCHAR(500) BINARY NOT NULL,
CONSTRAINT `MAUTHZPATHSMAPPING_PATHS_PK` PRIMARY KEY
(`AUTHZ_OBJ_ID_OID`,`PATHS`)
) ENGINE=INNODB;
{noformat}
We need to evaluate if we need PATHS part of primary key and take appropriate
direction.
> DB Schme Init is failing on sentry HA branch
>
>
> Key: SENTRY-1614
> URL: https://issues.apache.org/jira/browse/SENTRY-1614
> Project: Sentry
> Issue Type: Bug
>Reporter: kalyan kumar kalvagadda
>
> When a schema tool is used to initialize sentry database schema we observing
> issue and the initialization of schema fails. Here are the details of the
> failure.
> *Error: Specified key was too long; max key length is 767 bytes*
> {noformat}
> Error: Specified key was too long; max key length is 767 bytes
> (state=42000,code=1071)
> Closing: 0: jdbc:mysql://192.168.56.103/sentry_db1
> org.apache.sentry.core.common.exception.SentryUserException: Schema
> initialization FAILED! Metastore state would be inconsistent !!
> *** Sentry schemaTool failed ***
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (SENTRY-1614) DB Schme Init is failing on sentry HA branch
[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839700#comment-15839700
]
kalyan kumar kalvagadda edited comment on SENTRY-1614 at 1/26/17 1:55 PM:
--
*Here is the analysis done:*
one of the tables added as part of sentry HA, MAUTHZPATHSMAPPING_PATHS had a
column of size VARCHAR(4000) as part of the primary key. This is the reason.
{noformat}
CREATE TABLE `MAUTHZPATHSMAPPING_PATHS`
(
`AUTHZ_OBJ_ID_OID` BIGINT NOT NULL,
`PATHS` VARCHAR(500) BINARY NOT NULL,
CONSTRAINT `MAUTHZPATHSMAPPING_PATHS_PK` PRIMARY KEY
(`AUTHZ_OBJ_ID_OID`,`PATHS`)
) ENGINE=INNODB;
{noformat}
We need to evaluate if we need PATHS part of primary key and take appropriate
direction.
was (Author: kkalyan):
Here is the analysis done:
one of the tables added as part of sentry HA, MAUTHZPATHSMAPPING_PATHS had a
column of size VARCHAR(4000) as part of the primary key. This is the reason.
{noformat}
CREATE TABLE `MAUTHZPATHSMAPPING_PATHS`
(
`AUTHZ_OBJ_ID_OID` BIGINT NOT NULL,
`PATHS` VARCHAR(500) BINARY NOT NULL,
CONSTRAINT `MAUTHZPATHSMAPPING_PATHS_PK` PRIMARY KEY
(`AUTHZ_OBJ_ID_OID`,`PATHS`)
) ENGINE=INNODB;
{noformat}
We need to evaluate if we need PATHS part of primary key and take appropriate
direction.
> DB Schme Init is failing on sentry HA branch
>
>
> Key: SENTRY-1614
> URL: https://issues.apache.org/jira/browse/SENTRY-1614
> Project: Sentry
> Issue Type: Bug
>Reporter: kalyan kumar kalvagadda
>
> When a schema tool is used to initialize sentry database schema we observing
> issue and the initialization of schema fails. Here are the details of the
> failure.
> *Error: Specified key was too long; max key length is 767 bytes*
> {noformat}
> Error: Specified key was too long; max key length is 767 bytes
> (state=42000,code=1071)
> Closing: 0: jdbc:mysql://192.168.56.103/sentry_db1
> org.apache.sentry.core.common.exception.SentryUserException: Schema
> initialization FAILED! Metastore state would be inconsistent !!
> *** Sentry schemaTool failed ***
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SENTRY-1614) DB Schme Init is failing on sentry HA branch
[
https://issues.apache.org/jira/browse/SENTRY-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839700#comment-15839700
]
kalyan kumar kalvagadda commented on SENTRY-1614:
-
Here is the analysis done:
one of the tables added as part of sentry HA, MAUTHZPATHSMAPPING_PATHS had a
column of size VARCHAR(4000) as part of the primary key. This is the reason.
{noformat}
CREATE TABLE `MAUTHZPATHSMAPPING_PATHS`
(
`AUTHZ_OBJ_ID_OID` BIGINT NOT NULL,
`PATHS` VARCHAR(500) BINARY NOT NULL,
CONSTRAINT `MAUTHZPATHSMAPPING_PATHS_PK` PRIMARY KEY
(`AUTHZ_OBJ_ID_OID`,`PATHS`)
) ENGINE=INNODB;
{noformat}
We need to evaluate if we need PATHS part of primary key and take appropriate
direction.
> DB Schme Init is failing on sentry HA branch
>
>
> Key: SENTRY-1614
> URL: https://issues.apache.org/jira/browse/SENTRY-1614
> Project: Sentry
> Issue Type: Bug
>Reporter: kalyan kumar kalvagadda
>
> When a schema tool is used to initialize sentry database schema we observing
> issue and the initialization of schema fails. Here are the details of the
> failure.
> *Error: Specified key was too long; max key length is 767 bytes*
> {noformat}
> Error: Specified key was too long; max key length is 767 bytes
> (state=42000,code=1071)
> Closing: 0: jdbc:mysql://192.168.56.103/sentry_db1
> org.apache.sentry.core.common.exception.SentryUserException: Schema
> initialization FAILED! Metastore state would be inconsistent !!
> *** Sentry schemaTool failed ***
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SENTRY-1614) DB Schme Init is failing on sentry HA branch
kalyan kumar kalvagadda created SENTRY-1614:
---
Summary: DB Schme Init is failing on sentry HA branch
Key: SENTRY-1614
URL: https://issues.apache.org/jira/browse/SENTRY-1614
Project: Sentry
Issue Type: Bug
Reporter: kalyan kumar kalvagadda
When a schema tool is used to initialize sentry database schema we observing
issue and the initialization of schema fails. Here are the details of the
failure.
*Error: Specified key was too long; max key length is 767 bytes*
{noformat}
Error: Specified key was too long; max key length is 767 bytes
(state=42000,code=1071)
Closing: 0: jdbc:mysql://192.168.56.103/sentry_db1
org.apache.sentry.core.common.exception.SentryUserException: Schema
initialization FAILED! Metastore state would be inconsistent !!
*** Sentry schemaTool failed ***
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
