WIP: scalar UDFs with metadata #1110
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timsaucer
force-pushed
the
feat/scalar-udf-metadata
branch
from
b06f381 to
d51aff1
Compare
kylebarron
reviewed
May 6, 2025
|
|
||
|
|
||
| class ScalarUDFExportable(Protocol): | ||
| """Type hint for object that has __datafusion_table_provider__ PyCapsule. |
There was a problem hiding this comment.
Suggested change
| """Type hint for object that has __datafusion_table_provider__ PyCapsule. | |
| """Type hint for object that has __datafusion_scalar_udf__ PyCapsule. |
| class ScalarUDFExportable(Protocol): | ||
| """Type hint for object that has __datafusion_table_provider__ PyCapsule. | ||
| https://datafusion.apache.org/python/user-guide/io/table_provider.html |
|
Superseded by #1145 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?