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

ASF GitHub Bot commented on TRAFODION-2160:
-------------------------------------------

GitHub user robertamarton opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/656

    [TRAFODION-2160]: Metadata upgrade failed with internal error in Priv…

    …MgrMD.cpp
    
    Fixed a check that verifies component privilege grants were sufficient 
during
    upgrade
    Updated expected results for privs2/TEST143

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertamarton/incubator-trafodion 
trafodion-2160

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/656.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #656
    
----
commit 5f1ca3885a33a3d3d711b3a70ebec9156855a1e0
Author: Roberta Marton <[email protected]>
Date:   2016-08-12T20:44:58Z

    [TRAFODION-2160]: Metadata upgrade failed with internal error in 
PrivMgrMD.cpp
    
    Fixed a check that verifies component privilege grants were sufficient 
during
    upgrade
    Updated expected results for privs2/TEST143

----


> Metadata upgrade failed with internal error in PrivMgrMD.cpp
> ------------------------------------------------------------
>
>                 Key: TRAFODION-2160
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2160
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-security
>            Reporter: Roberta Marton
>            Assignee: Roberta Marton
>
> Metadata Upgrade: failed
>  
>  
> *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrMD.cpp 
> on line 326.  DETAILS(Expecting 133 component privileges, instead 140 were 
> found.).
>  



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

Reply via email to