[jira] [Commented] (AMBARI-14144) FK_permission_roleauthorization_permission_id is too long for a constraint identifier

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-14144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035293#comment-15035293 ] 

Hadoop QA commented on AMBARI-14144:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12775190/AMBARI-14144_trunk_01.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4448//console

This message is automatically generated.

> FK_permission_roleauthorization_permission_id is too long for a constraint identifier
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14144
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14144
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.3.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: rbac
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-14144_trunk_01.patch
>
>
> {noformat}
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id) REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 00000 -  "identifier is too long"
> *Cause:    An identifier with more than 30 characters was specified.
> *Action:   Specify at most 30 characters.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)