-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Making the recursive
dependency an optional feature
#13766
Comments
I have experienced a similar problem for wasm, #13513. After disabling it, got no problem. |
@blaginin has a PR to add recursive to sqlparser-rs as well: Perhaps we can follow his model for making this feature optional in DataFusion |
recursive
dependency an optional featurerecursive
dependency an optional feature
I have added this ticket to the the list of things we should fix before 44 release: #13334 |
FYI @peter-toth |
Sounds simple. @berkaysynnada would you like to make a PR? |
cc @buraksenn |
Seems like |
Thanks for the heads up @berkaysynnada . Opened a PR to make it optional |
take |
i’m curious if there are any cases when downstream can’t use recursive yet needs stack overflow protection 🤔 if so, we may need switch to iterative after all |
I think the challenge will be that converting algorithms to an iterative approach is non trivial effort and will likely complicate the code. So if people can't use recursive but need more efficient stack usage, perhaps they can contribute changes to help improve DataFusion in this area |
Is your feature request related to a problem or challenge?
The addition of the
recursive
crate as a dependency in #13310 may cause issues for some downstream projects.For example, in the DataFusion Comet subproject, we started to see CI failures when running with
miri
.For now, we disabled the miri checks, but we would prefer to keep them and opt out of the
recursive
feature when testing in CI.Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: