Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Integrate `datafusion-distributed` with `datafusion-python`

未关闭
#1,612 16 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
python, rust

调研方向

首先审查 pull request #1611 中尝试进行的集成,以及现有的 datafusion-python 和 datafusion-distributed API。比较提出的三种依赖关系和 API 安排,然后检查该尝试中包含的示例和测试。当达成一致的集成方向,使 Python 能够执行分布式查询,同时避免不必要的 API 更改时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

enhancement

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Allow running distributed queries in datafusion-python

Describe the solution you'd like

Ideally something well integrated with datafusion-python that does not require big changes or using different APIs for executing distributed queries.

datafusion-python is already a very ergonomic wrapper for using datafusion, so something maintaining that philosophy without introducing a lot of API surface would be ideal.

I'm interested specifically in using the datafusion-distributed library from within Python, and I see three mutually exclusive ways of integrating it:

  • Make datafusion-python depend on datafusion-distributed, hiding some internal plumbing in datafusion-python and extending the current API with distributed capabilities.
  • Create an external crate that depends on both datafusion-distributed and datafusion-python that ships an external API for using distributed functionality in datafusion-python
  • Make datafusion-distributed depend on datafusion-python, providing a set of functions and classes that decorate datafusion-python with distributed capabilities

I'm not sure which approach aligns best with this project's philosophy, the naive intuition from someone unfamiliar with this project is that the first option has greater chances of providing a well integrated experience, and it's probably the easiest to implement due to the fact that internal plumbing in the Rust world can be hidden in this project.

I actually tried this here:

And the fact that with only ~1K LOC, examples and tests included, can yield a functional integration, makes me think that it might actually not be a bad idea. But again, I don't know what I don't know, so would very gladly accept feedback and suggestions on something different.

主要语言
Python
星标
605
派生
176
平均合并
1 天 23 小时
30 天内合并 PR
8

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/datafusion-python 的其他 Issue

查看 apache/datafusion-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。