Uh oh!
There was an error while loading. Please reload this page.
Consolidate and document SQL AST shims - #22094
Conversation
| } | ||
| } | ||
| #[derive(Clone, PartialEq, Eq, PartialOrd, Hash, Debug)] |
There was a problem hiding this comment.
this stuff is all moved to sql.rs and I put a module level comment on it
timsaucer
left a comment
There was a problem hiding this comment.
This is a nice cleanup, and something I wasn't 100% happy with when I did it. Thank you!
| // specific language governing permissions and limitations | ||
| // under the License. | ||
| //! Local copies of [`sqlparser::ast`] structures |
There was a problem hiding this comment.
this is the documentation that explains what is going on
Since I think this will conflict with @andygrove 's upgrade of sqlparser and I don't think it will be potentially controversial, I am mergeing now |
…fusion into alamb/comments_about_sql_copy
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
alamb
commented
May 11, 2026
Merge was failing due to |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
alamb
commented
May 12, 2026
Thanks @xudong963 |
## Which issue does this PR close? - Related to apache#22069 ## Rationale for this change While upgrading sqlparser, it was not clear why there were feature gates for the `sql` feature: https://github.com/apache/datafusion/pull/22069/changes#r3204705488 There is a mode to avoid the `sqlparser` dependency, added by @timsaucer in - apache#17332 I think this feature makes sense but it is a little hard to understand because it is implemented with a bunch of `#[cfg(not(feature = "sql"))]` and there is no central place that explains the design. ## What changes are included in this PR? 1. Consolidate the SQL AST shim structures in a separate module 2. Document the design so it is easier to understand ## Are these changes tested? Yes by CI ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Which issue does this PR close?
Rationale for this change
While upgrading sqlparser, it was not clear why there were feature gates for the
sqlfeature: https://github.com/apache/datafusion/pull/22069/changes#r3204705488There is a mode to avoid the
sqlparserdependency, added by @timsaucer insqlfeature to make sql planning optional #17332I think this feature makes sense but it is a little hard to understand because it is implemented with a bunch of
#[cfg(not(feature = "sql"))]and there is no central place that explains the design.What changes are included in this PR?
Are these changes tested?
Yes by CI
Are there any user-facing changes?