Skip to content

Commit e571e45

Browse files
committed
Add clarification about extension APIs. Thanks @ozankabak
1 parent 5367040 commit e571e45

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

‎docs/source/contributor-guide/architecture.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,14 @@ work with you to design a new general purpose API. There are often others are
5555
interested in similar extensions and the act of defining the API often improves
5656
the code overall for everyone.
5757

58+
Extension APIs that provide "safe" default behaviors are more likely to be
59+
suitable for inclusion in DataFusion, while APIs that require major changes to
60+
built-in operators are likely less likely. For example, it might make less sense
61+
to add an API to support a stream processing feature if that would result in
62+
slower performance for built-in operators. It may still make sense to add
63+
extension APIs for such features, but leave implementation of such operators in
64+
downstream projects.
65+
5866
The process to create a new extension API is typically:
5967

6068
- Look for an existing issue describing what you want to do, and file one if it

0 commit comments

Comments
 (0)