You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/17 20:07:01 UTC

[jira] [Resolved] (AIRFLOW-709) Ariflow initdb sub-command will not run agains MS-SQL 2012

     [ https://issues.apache.org/jira/browse/AIRFLOW-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aizhamal Nurmamat kyzy resolved AIRFLOW-709.
--------------------------------------------
    Resolution: Fixed

Setting issues to resolved, as they were already. Moving to database component.

> Ariflow initdb sub-command will not run agains MS-SQL 2012
> ----------------------------------------------------------
>
>                 Key: AIRFLOW-709
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-709
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: cli, db
>    Affects Versions: 1.6.2, 1.7.0, 1.7.1, 1.7.1.2, 1.7.1.3, 1.8.0, 2.0.0
>         Environment: Airflow Environment:
> Distributor ID: Ubuntu
> Description:    Ubuntu 14.04.5 LTS
> Release:        14.04
> Codename:    trusty
> Backend:
> SQL Server 2012 SP3
>            Reporter: Chad T Henderson
>            Assignee: Chad T Henderson
>            Priority: Major
>
> When trying to run initdb for a MS-SQL 2012 backend, my the alembic migrations freeze almost immediately.
> After querying the database for blocking queries, I discovered that this query:
> CREATE TABLE alembic_version (
> 	version_num VARCHAR(32) NOT NULL
> )
>  
> was blocking this query.
> SELECT [INFORMATION_SCHEMA].[TABLES].[TABLE_NAME] 
> FROM [INFORMATION_SCHEMA].[TABLES] 
> WHERE [INFORMATION_SCHEMA].[TABLES].[TABLE_SCHEMA] = CAST('dbo' AS NVARCHAR(max)) AND [INFORMATION_SCHEMA].[TABLES].[TABLE_TYPE] = 'BASE TABLE' ORDER BY [INFORMATION_SCHEMA].[TABLES].[TABLE_NAME]
> I attempted to let the migrations run for ~45 minutes (multiple times) and it did not appear that the blocking was going to resolve itself.
> Each query was running under a separate session, which is what I believe is the cause of the blocking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)