This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 578a9eebbc Publish built docs triggered by
668984e9c73c21e7fca204f818ce613bd3d90d4d
578a9eebbc is described below
commit 578a9eebbccbe24daac8f0b413d01b3615c364de
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon Dec 16 14:02:52 2024 +0000
Publish built docs triggered by 668984e9c73c21e7fca204f818ce613bd3d90d4d
---
_sources/contributor-guide/index.md.txt | 38 +++++++++++++++++++++-----
contributor-guide/index.html | 47 ++++++++++++++++++++++++---------
searchindex.js | 2 +-
3 files changed, 67 insertions(+), 20 deletions(-)
diff --git a/_sources/contributor-guide/index.md.txt
b/_sources/contributor-guide/index.md.txt
index 4645fe5c88..0fe86c174a 100644
--- a/_sources/contributor-guide/index.md.txt
+++ b/_sources/contributor-guide/index.md.txt
@@ -58,7 +58,7 @@ unable to make progress you should unassign the issue by
using the `unassign me`
link at the top of the issue page (and ask for help if are stuck) so that
someone else can get involved in the work.
-### File Tickets to Discuss New Features
+### Discussing New Features
If you plan to work on a new feature that doesn't have an existing ticket, it
is
a good idea to open a ticket to discuss the feature. Advanced discussion often
@@ -70,15 +70,39 @@ line PR.
If you open a ticket and it doesn't get any response, you can try
`@`-mentioning
recently active community members in the ticket to get their attention.
-### What Features are Good Fits for DataFusion?
+### What Contributions are Good Fits?
-DataFusion is designed to highly extensible, and many features can be
implemented
-as extensions without changing the core of DataFusion.
+DataFusion is designed to be highly extensible, and many features can be
+implemented as extensions without changes or additions to the core. Support for
+new functions, data formats, and similar functionality can be added using those
+extension APIs, and there are already many existing community supported
+extensions listed in the [extensions list].
-We are [working on criteria for what features are good fits for DataFusion],
and
-will update this section when we have more to share.
+Query engines are complex pieces of software to develop and maintain. Given our
+limited maintenance bandwidth, we try to keep the DataFusion core as simple and
+focused as possible, while still satisfying the [design goal] of an easy to
+start initial experience.
-[working on criteria for what features are good fits for datafusion]:
https://github.com/apache/datafusion/issues/12357
+With that in mind, contributions that meet the following criteria are more
likely
+to be accepted:
+
+1. Bug fixes for existing features
+2. Test coverage for existing features
+3. Documentation improvements / examples
+4. Performance improvements to existing features (with benchmarks)
+5. "Small" functional improvements to existing features (if they don't change
existing behavior)
+6. Additional APIs for extending DataFusion's capabilities
+7. CI improvements
+
+Contributions that will likely involve more discussion (see Discussing New
+Features above) prior to acceptance include:
+
+1. Major new functionality (even if it is part of the "standard SQL")
+2. New functions, especially if they aren't part of "standard SQL"
+3. New data sources (e.g. support for Apache ORC)
+
+[extensions list]: ../library-user-guide/extensions.md
+[design goal]:
https://docs.rs/datafusion/latest/datafusion/index.html#design-goals
# Developer's guide
diff --git a/contributor-guide/index.html b/contributor-guide/index.html
index 2b1502cb06..07598a73a4 100644
--- a/contributor-guide/index.html
+++ b/contributor-guide/index.html
@@ -519,13 +519,13 @@
</a>
</li>
<li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link"
href="#file-tickets-to-discuss-new-features">
- File Tickets to Discuss New Features
+ <a class="reference internal nav-link" href="#discussing-new-features">
+ Discussing New Features
</a>
</li>
<li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link"
href="#what-features-are-good-fits-for-datafusion">
- What Features are Good Fits for DataFusion?
+ <a class="reference internal nav-link"
href="#what-contributions-are-good-fits">
+ What Contributions are Good Fits?
</a>
</li>
</ul>
@@ -656,8 +656,8 @@ unable to make progress you should unassign the issue by
using the <code class="
link at the top of the issue page (and ask for help if are stuck) so that
someone else can get involved in the work.</p>
</section>
-<section id="file-tickets-to-discuss-new-features">
-<h3>File Tickets to Discuss New Features<a class="headerlink"
href="#file-tickets-to-discuss-new-features" title="Link to this
heading">¶</a></h3>
+<section id="discussing-new-features">
+<h3>Discussing New Features<a class="headerlink"
href="#discussing-new-features" title="Link to this heading">¶</a></h3>
<p>If you plan to work on a new feature that doesn’t have an existing ticket,
it is
a good idea to open a ticket to discuss the feature. Advanced discussion often
helps avoid wasted effort by determining early if the feature is a good fit for
@@ -667,12 +667,35 @@ line PR.</p>
<p>If you open a ticket and it doesn’t get any response, you can try <code
class="docutils literal notranslate"><span
class="pre">@</span></code>-mentioning
recently active community members in the ticket to get their attention.</p>
</section>
-<section id="what-features-are-good-fits-for-datafusion">
-<h3>What Features are Good Fits for DataFusion?<a class="headerlink"
href="#what-features-are-good-fits-for-datafusion" title="Link to this
heading">¶</a></h3>
-<p>DataFusion is designed to highly extensible, and many features can be
implemented
-as extensions without changing the core of DataFusion.</p>
-<p>We are <a class="reference external"
href="https://github.com/apache/datafusion/issues/12357";>working on criteria
for what features are good fits for DataFusion</a>, and
-will update this section when we have more to share.</p>
+<section id="what-contributions-are-good-fits">
+<h3>What Contributions are Good Fits?<a class="headerlink"
href="#what-contributions-are-good-fits" title="Link to this heading">¶</a></h3>
+<p>DataFusion is designed to be highly extensible, and many features can be
+implemented as extensions without changes or additions to the core. Support for
+new functions, data formats, and similar functionality can be added using those
+extension APIs, and there are already many existing community supported
+extensions listed in the <a class="reference internal"
href="../library-user-guide/extensions.html"><span class="std
std-doc">extensions list</span></a>.</p>
+<p>Query engines are complex pieces of software to develop and maintain. Given
our
+limited maintenance bandwidth, we try to keep the DataFusion core as simple and
+focused as possible, while still satisfying the <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/index.html#design-goals";>design
goal</a> of an easy to
+start initial experience.</p>
+<p>With that in mind, contributions that meet the following criteria are more
likely
+to be accepted:</p>
+<ol class="arabic simple">
+<li><p>Bug fixes for existing features</p></li>
+<li><p>Test coverage for existing features</p></li>
+<li><p>Documentation improvements / examples</p></li>
+<li><p>Performance improvements to existing features (with benchmarks)</p></li>
+<li><p>“Small” functional improvements to existing features (if they don’t
change existing behavior)</p></li>
+<li><p>Additional APIs for extending DataFusion’s capabilities</p></li>
+<li><p>CI improvements</p></li>
+</ol>
+<p>Contributions that will likely involve more discussion (see Discussing New
+Features above) prior to acceptance include:</p>
+<ol class="arabic simple">
+<li><p>Major new functionality (even if it is part of the “standard
SQL”)</p></li>
+<li><p>New functions, especially if they aren’t part of “standard SQL”</p></li>
+<li><p>New data sources (e.g. support for Apache ORC)</p></li>
+</ol>
</section>
</section>
</section>
diff --git a/searchindex.js b/searchindex.js
index db6a61fc06..693dd0908d 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles": {"!=": [[48, "op-neq"]], "!~": [[48,
"op-re-not-match"]], "!~*": [[48, "op-re-not-match-i"]], "!~~": [[48, "id18"]],
"!~~*": [[48, "id19"]], "#": [[48, "op-bit-xor"]], "%": [[48, "op-modulo"]],
"&": [[48, "op-bit-and"]], "(relation, name) tuples in logical fields and
logical columns are unique": [[9,
"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]], "*":
[[48, "op-multiply"]], "+": [[48, "op-plus"]], "-": [[48, "op-minus"]], "/":
[[4 [...]
\ No newline at end of file
+Search.setIndex({"alltitles": {"!=": [[48, "op-neq"]], "!~": [[48,
"op-re-not-match"]], "!~*": [[48, "op-re-not-match-i"]], "!~~": [[48, "id18"]],
"!~~*": [[48, "id19"]], "#": [[48, "op-bit-xor"]], "%": [[48, "op-modulo"]],
"&": [[48, "op-bit-and"]], "(relation, name) tuples in logical fields and
logical columns are unique": [[9,
"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]], "*":
[[48, "op-multiply"]], "+": [[48, "op-plus"]], "-": [[48, "op-minus"]], "/":
[[4 [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
