Bug 1118403 - [doc] Pathname Usage Patterns with Federations
Summary: [doc] Pathname Usage Patterns with Federations
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Administration_Guide
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Divya
QA Contact: BigData QE
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-10 15:39 UTC by Ondřej Komárek
Modified: 2016-02-01 16:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-02-01 16:21:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Ondřej Komárek 2014-07-10 15:39:12 UTC
Description of problem:
It should be documented how to properly use pathname patterns. It can be described similarly as in hadoop documentation[1].

Point of this is to inform reader, that using glusterfs:/ or glusterfs:// is different from each other and it expects different format of path to file.

[1]: http://hadoop.apache.org/docs/r2.4.1/hadoop-project-dist/hadoop-hdfs/ViewFs.html (New World – Federation and ViewFs -> Pathname Usage Patterns)

Additional info:

Try to consider documenting other related special usages like just // (error) or using glusterfs:/// (or more slashes == same as one) etc.

Comment 1 Steve Watt 2014-07-24 00:10:25 UTC
I have added this information to the GA Administration Guide - https://mojo.redhat.com/docs/DOC-958040

Comment 2 Ondřej Komárek 2014-07-24 08:57:27 UTC
Text added to documentation clarifies using glusterfs:// prefix well. I think that could be mentioned usage of glusterfs:/. Nothing complex, just few words about fact, that using glusterfs: prefix with one, or more than two slashes differs in behaviour from glusterfs:// -> volume name is not expected in path in that case.

If you agree that this behaviour could be confusing for some users and it is important enough to mention it, please add info about this to DOC. Otherwise, put this BZ again to MODIFIED.

Comment 5 Steve Watt 2016-02-01 16:21:08 UTC
This solution is no longer available from Red Hat.

Note You need to log in before you can comment on or make changes to this bug.