Add booleans support to the CASE statement #1161
Merged
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
Dandandan
approved these changes
Oct 21, 2021
houqp
approved these changes
Oct 21, 2021
Member
|
thanks @xudong963 |
Contributor
|
😮 I think that may be the fast time between "file" and "fix" 👍 🐎 |
H0TB0X420
pushed a commit
to H0TB0X420/datafusion
that referenced
this pull request
Oct 7, 2025
…pache#1161) * docs: unify dataframe documentation (apache#2) * docs: update links in basics and rendering documentation * docs: add API reference section to main index * docs: add license information to rendering documentation * Move API Reference under User Guide > Dataframe * Merge data from dataframe api reference page into main dataframe page --------- Co-authored-by: Tim Saucer <timsaucer@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 #1156
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?