You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Elwin Arens (Jira)" <ji...@apache.org> on 2020/04/20 12:40:00 UTC

[jira] [Commented] (AIRFLOW-6366) Fix migrations for MS SQL Server

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

Elwin Arens commented on AIRFLOW-6366:
--------------------------------------

This issue has regressed in [https://github.com/apache/airflow/blob/1.10.10/airflow/migrations/versions/852ae6c715af_add_rendered_task_instance_fields_table.py]

> Fix migrations for MS SQL Server
> --------------------------------
>
>                 Key: AIRFLOW-6366
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6366
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: database
>    Affects Versions: 1.10.7
>            Reporter: Bjorn Olsen
>            Assignee: Bjorn Olsen
>            Priority: Minor
>             Fix For: 1.10.8
>
>
> Although MS SQL Server is not officially supported as a backend database, I am using it via PyODBC and found a minor issue with migration from 1.10.6 to 1.10.7.
>  
> Below is a log excerpt showing the issue:
> INFO [alembic.runtime.migration] Running upgrade 6e96a59344a4 -> d38e04c12aa2, add serialized_dag table
> sqlalchemy.exc.ProgrammingError: (pyodbc.ProgrammingError) ('42000', "[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]'JSON_VALID' is not a recognized built-in function name. (195) (SQLExecDirectW)")



--
This message was sent by Atlassian Jira
(v8.3.4#803005)