Skip to content

Additional fix for writing output in DatabricksSqlOperator#27897

Closed
alexott wants to merge 1 commit into
apache:mainfrom
alexott:further-fix-databricks-sql-operator
Closed

Additional fix for writing output in DatabricksSqlOperator#27897
alexott wants to merge 1 commit into
apache:mainfrom
alexott:further-fix-databricks-sql-operator

Conversation

@alexott

@alexott alexott commented Nov 24, 2022

Copy link
Copy Markdown
Contributor

This PR adds fix for writing results in DatabricksSqlOperator

@potiuk

potiuk commented Nov 25, 2022

Copy link
Copy Markdown
Member

As dicussed before @alexott I think Better (and more future proof, covering comprehensively all DB and DBAPI SQL Operator functionality with many tests ) solution is in #27912 - but there are some questions to answer there.

@potiuk

potiuk commented Dec 3, 2022

Copy link
Copy Markdown
Member

Superseded by #27912 and follow-ups.

@potiuk potiuk closed this Dec 3, 2022
@alexott alexott deleted the further-fix-databricks-sql-operator branch January 11, 2023 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants