Uh oh!
There was an error while loading. Please reload this page.
ARROW-10998: [C++] Detect URIs where a filesystem path is expected - #11997
ARROW-10998: [C++] Detect URIs where a filesystem path is expected#11997pitrou wants to merge 3 commits into
Conversation
An occasional misunderstanding is to pass a URI to filesystem methods, where a regular path is expected. Make these situations easier to diagnose by raising a specific error.
pitrou
commented
Dec 20, 2021
@coryan Would you like to take a look at the GCS changes here? |
coryan
left a comment
There was a problem hiding this comment.
LGTM, with a minor nit in the tests.
| TEST_F(GcsIntegrationTest, OpenInputStreamUri) { | ||
| auto fs = internal::MakeGcsFileSystemForTest(TestGcsOptions()); | ||
| ASSERT_RAISES(Invalid, fs->OpenInputStream("gcs:" + PreexistingObjectPath())); |
There was a problem hiding this comment.
I know this is just for testing purposes, but the conventional prefix for GCS is gs://, at least that is what gsutil uses:
There was a problem hiding this comment.
I see, thank you.
By the way, it seems other packages have adopted the gcs:// convention: https://gcsfs.readthedocs.io/en/latest/#integration
There was a problem hiding this comment.
Sigh... My guess (and let me stress that this would be just a guess) is that gs:// is more familiar to GCS users. I can live with gcs:// too
There was a problem hiding this comment.
Ah, it looks like they accept gs:// too: https://github.com/fsspec/gcsfs/blob/main/gcsfs/core.py#L1171
westonpace
left a comment
There was a problem hiding this comment.
Seems like a reasonable change to me. Maybe drop a note that colons are not supported in filenames here (https://github.com/apache/arrow/blob/master/docs/source/cpp/io.rst#filesystems) where we mention . and .. are not supported?
| static Result<S3Path> FromString(const std::string& s) { | ||
| if (internal::IsLikelyUri(s)) { | ||
| return Status::Invalid( | ||
| "Expected a S3 object path of the form 'bucket/key...', got a URI: '", s, "'"); |
There was a problem hiding this comment.
| "Expected a S3 object path of the form 'bucket/key...', got a URI: '", s, "'"); | |
| "Expected an S3 object path of the form 'bucket/key...', got a URI: '", s, "'"); |
pitrou
commented
Dec 20, 2021
Hmm, they should be more or less supported except in the first segment of a path. |
Benchmark runs are scheduled for baseline = cfcce5a and contender = 238b363. 238b363 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
jorisvandenbossche
commented
Dec 23, 2021
Cool, this is a nice usability improvement! |
An occasional misunderstanding is to pass a URI to filesystem methods, where a regular path is expected.
Make these situations easier to diagnose by raising a specific error.