mchades commented on code in PR #6724:
URL: https://github.com/apache/gravitino/pull/6724#discussion_r2011510896


##########
docs/manage-fileset-metadata-using-gravitino.md:
##########
@@ -320,24 +320,41 @@ Currently, Gravitino supports two **types** of filesets:
 The `storageLocation` is the physical location of the fileset. Users can 
specify this location
 when creating a fileset, or follow the rules of the catalog/schema location if 
not specified.
 
+The `storageLocation` in each level can contain **placeholders**, format as 
`{{name}}`, which will
+be replaced by the corresponding fileset property value when the fileset 
object is created. The
+placeholder property in the fileset object is formed as 
"placeholder-{{name}}". For example, if
+the `storageLocation` is `file:///tmp/{{schema}}-{{fileset}}-{{verion}}`, and 
the fileset object 
+named "catalog1.schema1.fileset1" contains the properties 
`placeholder-version=v1`, 
+the actual `storageLocation` will be `file:///tmp/schema1-fileset1-v1`.
+
 The value of `storageLocation` depends on the configuration settings of the 
catalog:
 - If this is a local fileset catalog, the `storageLocation` should be in the 
format of `file:///path/to/fileset`.
 - If this is a HDFS fileset catalog, the `storageLocation` should be in the 
format of `hdfs://namenode:port/path/to/fileset`.
 
 For a `MANAGED` fileset, the storage location is:
 
-1. The one specified by the user during the fileset creation.
-2. When the catalog property `location` is specified but the schema property 
`location` isn't specified,
-   the storage location is `catalog location/schema name/fileset name`.
+1. The one specified by the user during the fileset creation, and the 
placeholder will be replaced by the
+   corresponding fileset property value.
+2. When the catalog property `location` is specified but the schema property 
`location` isn't specified, the storage location is:
+   1. `catalog location/schema name/fileset name` if `catalog location` does 
not contain any placeholder. 
+   2. `catalog location` - placeholders in the catalog location will be 
replaced by the corresponding fileset property value.
+
 3. When the catalog property `location` isn't specified but the schema 
property `location` is specified,
-   the storage location is `schema location/fileset name`.
+   the storage location is:
+   1. `schema location/fileset name` if `schema location` does not contain any 
placeholder.
+   2. `schema location` - placeholders in the schema location will be replaced 
by the corresponding fileset property value.

Review Comment:
   This is a common usage of the `-`, with the latter providing additional 
explanation for the former.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to