yuqi1129 opened a new pull request, #12434: URL: https://github.com/apache/gravitino/pull/12434
### What changes were proposed in this pull request? Restructures the fileset catalog documentation along a single axis: shared reference material lives in exactly one place, while each per-backend page keeps a complete runnable path. - `fileset-catalog.md` becomes the shared reference and gains a storage-backend table (bundle jar, location scheme, backend properties) in place of a bare list of links. - The five per-backend pages are generated from one template so they stay strictly parallel. Each merges the three former property tables (catalog, Java client, Python client) into one — which also makes the hyphen-vs-underscore difference visible at a glance — and drops the deprecated `filesystem-providers` / `default-filesystem-provider` rows that were listed as required. - Each page uses one consistent set of names end to end, so the examples can be run in order. Corrections made along the way: - A missing comma in the Python catalog properties dict. - A schema example that loaded `hive_catalog` instead of the catalog it had just created. - `SparkSession.builder` chains with no line continuations, which could not be run as written. - A stray quote in the Python GVFS example. - `hadoop dfs` replaced with `hadoop fs`. - The Java client section linking to the Python client's anchor. - Four dead anchors left by the earlier `manage-*` page split: `#catalog-operations`, `#schema-operations`, `#placeholder` and `#manage-filesets-across-multiple-clusters`. - Tencent Cloud COS missing from the index page and from the GVFS page. This is an alternative take on #12399. That PR removes the duplication between the five per-backend pages, which is real — 116 lines are byte-identical across all five of them. The difference here is where the removed procedure lands: this PR keeps it on each backend page rather than consolidating it away, on the view that a page a newcomer follows to get something running is worth duplicating, while property semantics and inheritance rules are not. ### Why are the changes needed? The per-backend pages could not be followed end to end. Names changed between steps, several code samples did not parse, and deprecated properties were marked as required. Anyone new to filesets had to reconstruct a working setup from three pages. ### Does this PR introduce _any_ user-facing change? Documentation only. No property keys or APIs change. ### How was this patch tested? - Checked code-fence, `Tabs`/`TabItem` and table-column balance across every touched page. - Verified that every intra-doc link and anchor into and out of the touched pages resolves. - Compiled every Python snippet on the touched pages. -- 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]
