mchades opened a new issue, #14878:
URL: https://github.com/apache/gravitino/issues/14878

   ### What would you like to be improved?
   
   The fileset guides show `storageLocation` and `storageLocations` separately. 
A mixed example would make it clear which paths a fileset inherits, which path 
GVFS uses by default, and which paths a managed drop deletes. The create guide 
also implies that an external fileset directory must already exist. [Original 
discussion in 
#14810](https://github.com/apache/gravitino/issues/14810#issuecomment-6761219238)
   
   ### How should we improve?
   
   - In `docs/open-api/filesets.yaml` and 
`docs/manage-fileset-metadata-using-gravitino.md`, show a create request using 
both fields. A non-null `storageLocation` sets the reserved `unknown` entry, 
overriding `storageLocations["unknown"]` and retaining the other named entries.
   - In `docs/fileset-catalog.md`, show how legacy `location` supplies 
`unknown` alongside `location-{name}`, even when two names refer to the same 
URI. Locations are merged by name. Fileset values override schema values, which 
override catalog values. Names omitted from a partial request are inherited.
   - Show the resulting map and select a default from it. With multiple 
resolved names, `default-location-name` must match one of them. The other 
locations remain available to GVFS. [GVFS location 
selection](https://github.com/apache/gravitino/blob/main/docs/how-to-use-gvfs.md#examples)
   - Clarify the lifecycle in `docs/filesets.md` and the create guide. With 
filesystem operations enabled, creating an external fileset can create missing 
directories. Dropping an external fileset preserves data. Dropping a managed 
fileset deletes data at every resolved fileset path. With 
`disable-filesystem-ops=true`, create and drop update metadata only.


-- 
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