-
Notifications
You must be signed in to change notification settings - Fork 2
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
object's full path should include zone name component #16
Comments
@hechth - I see this as centering on the interpretation of the path parameter in the In the case that you find your application "prefers" the zone-relative interpretation you've chosen for paths, .... then @trel ,does this seem logical to you as it does to me? |
Agreed, not using the zone name in the path means visibility across federation is off the table. |
There is also this line which actually examines the path's content (its leading element in particular) in order to tell whether or not it should be considered absolute. That probably shouldn't be so. It is after all technically possible for a Because of this, we get e.g. the erroneous result (in a default iRODS install having zone name
Yet another reason why I see it as desirable to unify the |
Taking a fresh look at this issue, I'm wondering if it's been partly misguided, ... mainly because I think the spirit of PyFilesystem2 is to present like a mount point, at least when taking the example of its use with a plain POSIX OS. In other words the |
Objects in the catalog are known and queried by logical path, ie the name,
It seems, in keeping with this, that getting the path of a given collection,etc, via an iRODSFS should yield the same.
However, we see this instead:
The zone-named leading components of the paths are missing.
The text was updated successfully, but these errors were encountered: