doc(server): sync backend-hbase with master - #477
Open
bitflicker64 wants to merge 1 commit into
Open
Conversation
Add the missing HBase backend configuration page in English and Chinese. It documents the supported HBase version, how to select the backend, all fifteen HbaseOptions keys with their defaults and value ranges grouped as the Options class groups them, the Kerberos settings, the namespace and table layout, the docker/hbase setup for local testing, and the features the backend reports as unsupported.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Syncs the HBase backend documentation with hugegraph master (
36811483a). The HBase backend had no page of its own: the only coverage was the option table inconfig-option.mdand four commented lines inconfig-guide.md, so the namespace and table layout, the Kerberos flow, the pre-split behavior, the supported HBase version and the localdocker/hbasesetup were undocumented.weight: 7, usingconfig-https.mdas the frontmatter and layout templatebackend=hbaseplusserializer=hbase, with a note on whybinaryis not equivalent, plus the note that arocksdb-onlybuild has no HBase providerHbaseOptionskeys with defaults, allowed ranges and the HBase property each one maps to, grouped as the Options class groups themhbase.hbase_site, and what the backend sets on the connection whenhbase.kerberos_enable=true; also thathbase.hbase_siteis loaded regardlessdefault_hugegraphby default), the three storesm/g/sand their table names, the singlefcolumn family, the aggregation coprocessor, which tables are pre-split, and theMmeta table kept across truncatedocker/hbasecompose flow, the advertised hostname variables, the five published ports, the maven profile to run the tests, and the teardown commandPaths in the source column are relative to the hugegraph repository root; the
Hbase*.javafiles without a directory live inhugegraph-server/hugegraph-hbase/src/main/java/org/apache/hugegraph/backend/store/hbase/.Only the two new pages are touched. Three problems found in pages owned by other modules are reported separately and left unedited: the
hbase.krb5_confdefault inconfig-option.mdis writtenetc/krb5.confinstead of/etc/krb5.conf,hbase.truncate_timeoutis missing from that table, and the hbase block quoted inconfig-guide.mdpredates thehbase.enable_partition/hbase.vertex_partitions/hbase.edge_partitionslines now in the shipped template.