Skip to content

Additional fix for writing output in DatabricksSqlOperator #27897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
alexott wants to merge 1 commit into from
Closed

Additional fix for writing output in DatabricksSqlOperator #27897

alexott wants to merge 1 commit into from

Conversation

@alexott
Copy link
Contributor

@alexott alexott commented Nov 24, 2022

This PR adds fix for writing results in DatabricksSqlOperator

@alexott alexott mentioned this pull request Nov 24, 2022
Closed
20 tasks
@potiuk
Copy link
Member

potiuk commented Nov 25, 2022

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
Copy link
Member

potiuk commented Dec 3, 2022

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

Reviewers

No reviews

Assignees

No one assigned

Labels

area:providers provider:databricks

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@alexott @potiuk