Register SQL planners in SessionState constructor
#11253
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
Contributor
|
I merged up from main and once CI passes I think this will be good to go |
comphead
pushed a commit
to comphead/arrow-datafusion
that referenced
this pull request
Jul 8, 2024
* Register SQL planners in SessionState constructor * update map capacity with user_defined_sql_planners ref count * formatting * undo last --------- Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
findepi
pushed a commit
to findepi/datafusion
that referenced
this pull request
Jul 16, 2024
* Register SQL planners in SessionState constructor * update map capacity with user_defined_sql_planners ref count * formatting * undo last --------- Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
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 #11216
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Since this is minor refactor existing test cases should do
Are there any user-facing changes?
Nope