You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the URIs must be of the form gs://bucket, and URIs with port, user info, path, query or fragment parts will fail.
This seems to be unnecessarily restrictive, and causes legitimate uses to fail - e.g. if we are trying to find a FileSystem for a given URI then we shouldn't have to know that GS is more restrictive than other providers, and remove everything from the URI except the scheme and host.
I suggest that the implementation accept the extra information in URIs and just ignore it.
The text was updated successfully, but these errors were encountered:
Currently the URIs must be of the form
gs://bucket
, and URIs with port, user info, path, query or fragment parts will fail.This seems to be unnecessarily restrictive, and causes legitimate uses to fail - e.g. if we are trying to find a FileSystem for a given URI then we shouldn't have to know that GS is more restrictive than other providers, and remove everything from the URI except the scheme and host.
I suggest that the implementation accept the extra information in URIs and just ignore it.
The text was updated successfully, but these errors were encountered: