Closed alamb closed 9 months ago
Related to https://github.com/apache/arrow-datafusion/issues/7357
We are sorting out how to split up DataFusion into smaller modules, and we hit https://github.com/apache/arrow-datafusion/issues/7357
There is a tension between knowing about datasources and separating out physical plan and datasources (see commentary on https://github.com/apache/arrow-datafusion/issues/7357 and linked PRs).
We thus propose to move this API upstream into Ballista. See https://github.com/apache/arrow-datafusion/pull/7487
No
Thanks @Dandandan
Which issue does this PR close?
Related to https://github.com/apache/arrow-datafusion/issues/7357
Rationale for this change
We are sorting out how to split up DataFusion into smaller modules, and we hit https://github.com/apache/arrow-datafusion/issues/7357
There is a tension between knowing about datasources and separating out physical plan and datasources (see commentary on https://github.com/apache/arrow-datafusion/issues/7357 and linked PRs).
We thus propose to move this API upstream into Ballista. See https://github.com/apache/arrow-datafusion/pull/7487
What changes are included in this PR?
Are there any user-facing changes?
No