Add 'Extensions List' page to the documentation#12420
Conversation
| we'll gladly set up a new repository for your extension. | ||
|
|
||
| | Name | Type | Description | | ||
| | ---------------------------- | ----------------- | --------------------------------------------------------------------------------- | |
There was a problem hiding this comment.
These were the most seemingly active projects that I could find in https://github.com/datafusion-contrib -- there may more that we should list here
phillipleblanc
left a comment
phillipleblanc
left a comment
There was a problem hiding this comment.
Excellent. I think this + encouraging people to start new extensions in datafusion-contrib + examples of integrating with extensions (like in datafusion-tui) will be really helpful.
I also wonder if we need some criteria for "graduating" an extension to be an official Apache DataFusion sub-project (i.e. similar to ballista/python bindings)? I realize that doesn't really solve the "maintainers being stretched thin" problem since it just means now more repos to monitor. Maybe the criteria is "if there are a subset of DataFusion committers that vote to maintain it longterm" ? Not important to solve now though imo.
ozankabak
left a comment
ozankabak
left a comment
There was a problem hiding this comment.
Looks great, thank you
Yes for sure -- @phillipleblanc we are actually doing this in term apache/datafusion-sqlparser-rs#1294 -- the procedural method is that we do a binding community vote. |
5 participants
Which issue does this PR close?
Related to #12357
Rationale for this change
Inspired by @phillipleblanc and @jonahgao comments on #12357 let's try and make it easier to find other features such as table providers rather than necessarily trying to add them to the core of DataFusion itself.
What changes are included in this PR?
Are these changes tested?
CI doc tests. I also rendered it locally:
Are there any user-facing changes?