[
https://issues.apache.org/jira/browse/AMBARI-15159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167783#comment-15167783
]
Hudson commented on AMBARI-15159:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #418 (See
[https://builds.apache.org/job/Ambari-branch-2.2/418/])
AMBARI-15159. DBAccessor metadata API for schema check calls can return
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4d8bc0f636dfef646b77cd7fe394ec697046d22c])
*
ambari-server/src/test/java/org/apache/ambari/server/orm/DBAccessorImplTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.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)
