Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Issues when using databricks-sql-connector==4.6.0

Open
  • Is something wrong?
#77 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python, sqlalchemy
Domain
databases

Research direction

Reproduce the failure with databricks-sqlalchemy 2.0.10, alembic 1.8.4, and databricks-sql-connector 4.6.0, then compare it with connector 4.2.6. Start by reading databricks/sqlalchemy/base.py and databricks/sqlalchemy/_parse.py, especially the result handling shown in the traceback. Done means schema migrations complete successfully with connector 4.6.0.

Written by the indexing model from the issue text.

Description

Hello there,

I am using databricks-sqlalchemy (2.0.10) in combination with alembic (1.8.4) in a CI/CD pipeline to automate schema migrations.

When our pipeline suddenly stopped working, i found out after some debugging, that alembic fails with an error message (see below) when using databricks-sql-connector==4.6.0. After pinning the sql connector to databricks-sql-connector==4.2.6 (the version it works with from my local machine), the migrations ran through again.

The corresponding part of my CI/CD pipeline log:

  File "/agent/_work/1/s/.venv/lib/python3.14/site-packages/databricks/sqlalchemy/base.py", line 382, in has_table
    self._describe_table_extended(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        connection=connection,
        ^^^^^^^^^^^^^^^^^^^^^^
    ...<2 lines>...
        schema_name=schema,
        ^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/agent/_work/1/s/.venv/lib/python3.14/site-packages/databricks/sqlalchemy/base.py", line 208, in _describe_table_extended
    fmt_result = _describe_table_extended_result_to_dict_list(result)
  File "/agent/_work/1/s/.venv/lib/python3.14/site-packages/databricks/sqlalchemy/_parse.py", line 40, in _describe_table_extended_result_to_dict_list
    for row in result.all():
               ~~~~~~~~~~^^
  File "/agent/_work/1/s/.venv/lib/python3.14/site-packages/sqlalchemy/engine/result.py", line 987, in all
    return self._allrows()
           ~~~~~~~~~~~~~^^
  File "lib/sqlalchemy/engine/_result_cy.py", line 366, in sqlalchemy.engine._result_cy.BaseResultInternal._allrows
  File "lib/sqlalchemy/engine/_result_cy.py", line 201, in sqlalchemy.engine._result_cy.BaseResultInternal._row_getter.many_rows_simple
  File "lib/sqlalchemy/engine/_row_cy.py", line 72, in sqlalchemy.engine._row_cy.BaseRow.__init__
TypeError: Expected tuple, got Row

Cheers,
Thomas

Dominant language
Python
Stars
24
Forks
20
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sqlalchemy

All issues in databricks/databricks-sqlalchemy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.