mchades commented on code in PR #14124: URL: https://github.com/apache/gravitino/pull/14124#discussion_r4344301769
########## docs/filesets.md: ########## @@ -44,8 +44,9 @@ than federating an external one, so no provider is needed when creating it. [Catalogs and Schemas](./catalogs-and-schemas.md). A fileset catalog usually carries a base `location`, and schemas can narrow it further. -**2. Create the fileset.** Give it a name, a type, and a storage location. Creating a managed -fileset creates the directory; pointing at an existing path makes it external. +**2. Create the fileset.** Give it a name, a type, and a storage location. Choose `MANAGED` to let +Gravitino manage the data lifecycle, or `EXTERNAL` to retain the data when the fileset is dropped. +Pointing at an existing path does not automatically make a fileset external. Review Comment: Creation behavior is unchanged. The previous quick-start wording incorrectly implied that an existing path makes a fileset external. I’ll clarify in the PR description that this is a documentation correction. -- 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]
