Skip to content
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

ARROW-8213: [Python][Dataset] Opening a dataset with a local incorrect path gives confusing error message #6854

Closed
wants to merge 3 commits into from

Conversation

kszucs
Copy link
Member

@kszucs kszucs commented Apr 6, 2020

Workaround until it is properly handled in the C++ implementation.

@github-actions
Copy link

github-actions bot commented Apr 6, 2020

@pitrou
Copy link
Member

pitrou commented Apr 7, 2020

Well, can you try to fix it in the C++ implementation? :-) Or do you want me to do it?

@jorisvandenbossche
Copy link
Member

Well, can you try to fix it in the C++ implementation? :-) Or do you want me to do it?

I thought you didn't want to deal with non-URIs on the C++ FileSystem level?

@pitrou
Copy link
Member

pitrou commented Apr 7, 2020

There's a C++ function called FileSystemFromUriOrPath. I don't remember why the Python side doesn't use it.

python/pyarrow/dataset.py Outdated Show resolved Hide resolved
@pitrou
Copy link
Member

pitrou commented Apr 7, 2020

@jorisvandenbossche Opinions on this?

@jorisvandenbossche
Copy link
Member

Thanks for that fix! Yeah, I think catching "empty scheme" in the error message is the most straightforward way to handle it

@kszucs
Copy link
Member Author

kszucs commented Apr 7, 2020

I don't like this kind of error handling because it is error prone, bound to an error message instead of an error type or kind - I'm fine with it as a workaround though.

Copy link
Member

@wesm wesm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, this seems okay to me, we can iterate/improve this logic surely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants