imbajin commented on code in PR #559:
URL: https://github.com/apache/hugegraph-doc/pull/559#discussion_r4505240611


##########
content/en/docs/guides/toplingdb.md:
##########
@@ -102,6 +110,28 @@ The launcher uses that component's `conf/toplingdb.yaml`. 
Set `TOPLINGDB_EASY_MI
 The shipped native profile disables its HTTP server and keeps 
`memtable_as_log_index=false`, which the Java write path requires.
 Tune that profile for the host; it is separate from the business provider and 
data-path configuration.
 
+Updated distributions use community-compatible SkipList memtables and 
BlockBasedTable files by default.

Review Comment:
   Addressed in 2b41f3a8f: the English and Chinese guides now explicitly 
require a build containing apache/hugegraph#3447 for the community-compatible 
profile and preparation validation. The docs should be merged after that 
implementation; current 1.7.0 release is not represented as shipping this 
profile.



##########
content/en/docs/guides/dev-test/toplingdb.md:
##########
@@ -104,6 +114,42 @@ The launcher uses that component's `conf/toplingdb.yaml`. 
Set `TOPLINGDB_EASY_MI
 The shipped native profile disables its HTTP server and keeps 
`memtable_as_log_index=false`, which the Java write path requires.
 Tune that profile for the host; it is separate from the business provider and 
data-path configuration.
 
+Starting with Server 1.8.0+ (master), distributions ship a community-native 
profile in `conf/toplingdb.yaml`

Review Comment:
   Addressed in 2b41f3a8f in both languages: profile availability is scoped to 
builds containing apache/hugegraph#3447; older development builds are 
distinguished, and Server 1.7.0 is correctly identified as lacking both the 
profile and prepare-topling.sh. The guide no longer claims the compatibility 
profile is already in master.



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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to