ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15159) DBAccessor metadata API for schema check calls can return more than 1 result
Date Fri, 26 Feb 2016 01:03:18 GMT

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

Hudson commented on AMBARI-15159:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4390 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4390/])
Revert "AMBARI-15159. DBAccessor metadata API for schema check calls can (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a4deda3477925d52df9fc95e7736b8b5d6fece81])
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
* ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java


> DBAccessor metadata API for schema check calls can return more than 1 result
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-15159
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15159
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>            Priority: Critical
>             Fix For: 2.2.2
>
>
> JDBC metadata calls should take into account current schema to filter possible collisions
when ambari users have permissions for multiple schemas.



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

Mime
View raw message