ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21648) Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.
Date Fri, 04 Aug 2017 08:38:00 GMT

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

Hudson commented on AMBARI-21648:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7845 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7845/])
AMBARI-21648. Do not use 'dbo' schema name in idempotent Ambari DDL (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98f15c94ee73c7d7ef938108772d3495e1d13e43])
* (edit) ambari-server/src/main/python/azuredb_create_generator.py


> Do not use 'dbo' schema name in idempotent Ambari DDL generator for AzureDB.
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-21648
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21648
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21648.v1.patch
>
>
> Ambari database tables can be created in any AzureDB schema beside the default 'dbo'.
The generated DDL sql will fail in case the Ambari database tables were to be created in other
schema than 'dbo' as it looks up db objects in 'dbo' schema only.
> If no schema is specified than db object will be looked up in the default schema of the
user.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message