yuqi1129 commented on PR #12399: URL: https://github.com/apache/gravitino/pull/12399#issuecomment-5237908485
@markhoerth Thanks for working on reducing the duplication. However, I think this PR has gone too far in consolidating these documents. The value of the per-cloud pages is not only to document the differences between storage backends. More importantly, they serve as self-contained, task-oriented quick-start guides. A newcomer can choose a storage backend and follow a single page end to end: create the catalog, schema, and fileset, and then access it through Python GVFS, Spark, or the Hadoop command line. In the consolidated version, most of these runnable workflows have been removed. Users now need to combine the property tables on this page with the generic GVFS documentation and infer the required backend-specific dependencies, jars, credentials, and configurations themselves. Even as someone familiar with Gravitino, I found it difficult to quickly get started from the simplified version. Also, how-to-use-gvfs.md currently relies on the pages being deleted for cloud-specific Java and Python configurations. Therefore, the generic document does not currently provide an equivalent replacement for the removed content. Some duplication is acceptable in tutorial and onboarding documentation because self-containedness is valuable to users. I suggest keeping the per-cloud quick-start pages, or otherwise preserving complete, runnable examples for Python GVFS, Spark, and Hadoop CLI for every supported backend. We can still consolidate the shared reference material and explanations, but I do not think we should remove the end-to-end user journey. -- 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]
