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
Cannot query S3 paths containing whitespace #2799
Comments
@tustvold Here is another potential object store bug that I found |
This is sadly intentional, https://docs.rs/object_store/latest/object_store/path/struct.Path.html#path-safety, I'm not really sure what can be done about this... |
We should add least add a check and throw an error? The S3 error response is somewhat obscure. It will be a shame if DataFusion and Ballista cannot support querying certain public data sets like nyc-tlc because they have spaces in paths. Other query engines support it. One example: https://coiled.io/blog/nyc-taxi-parquet-csv-index-error/ I will plan on digging into this more soon to understand the issue better. |
Agreed, I would have expected DataFusion to refuse that query as the parquet location is not a valid URL. Possibly ListingTableUrl is escaping rather than parsing.
I welcome alternative suggestions for how to handle path escaping |
Perhaps some kind of user-provided config to override the default behavior? I will take a look this weekend. |
Actually looking into this, we don't disallow spaces in paths, I think this might be a DataFusion bug 🤔 |
There is a somewhat related issue I ran into when playing with this, but you most definitely can create, read, etc... objects with paths containing spaces - #2800 |
I think this was fixed by #2801 |
Describe the bug
I cannot register a path containing a space.
It works if I change the path to not have spaces:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: