dbt-labs / dbt-external-tables

dbt macros to stage external sources
https://hub.getdbt.com/dbt-labs/dbt_external_tables/latest/
Apache License 2.0
288 stars 116 forks source link

`io.delta.exceptions.ProtocolChangedException` in CI for Databricks #228

Closed dbeatty10 closed 5 months ago

dbeatty10 commented 11 months ago

Describe the bug

Getting the following error message with CI for Databricks:

error message: 'org.apache.hive.service.cli.HiveSQLException: Error running query: io.delta.exceptions.ProtocolChangedException: The protocol version of the Delta table has been changed by a concurrent update.

Steps to reproduce

Run CI.

Actual results

Example:

13:38:44  1 of 1 START seed file dbt_external_tables_integration_tests_databricks.people . [RUN]
13:38:50  1 of 1 ERROR loading seed file dbt_external_tables_integration_tests_databricks.people  [ERROR in 6.17s]
13:38:50  
13:38:50  Finished running 1 seed in 0 hours 1 minutes and 46.21 seconds (106.21s).
13:38:50  
13:38:50  Completed with 1 error and 0 warnings:
13:38:50  
13:38:50  Runtime Error in seed people (seeds/people.csv)
13:38:50    ('HY000', "[HY000] [Simba][Hardy] (35) Error from server: error code: '0' error message: 'org.apache.hive.service.cli.HiveSQLException: Error running query: io.delta.exceptions.ProtocolChangedException: The protocol version of the Delta table has been changed by a concurrent update. This happens when multiple writers are writing to an empty di'. (35) (SQLExecDirectW)")
13:38:50 

Screenshots and log output

image

System information

The contents of your packages.yml file:

Which database are you using dbt with?

The output of dbt --version:

<output goes here>

The operating system you're using:

The output of python --version:

Additional context

github-actions[bot] commented 5 months ago

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

github-actions[bot] commented 5 months ago

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.