liuxiaocs7 commented on code in PR #270:
URL: 
https://github.com/apache/incubator-hugegraph-doc/pull/270#discussion_r1226288422


##########
content/cn/docs/config/config-guide.md:
##########
@@ -259,46 +259,97 @@ cassandra.password=
 
 ### 5 多图配置
 
-我们的系统是可以存在多个图的,并且各个图的后端可以不一样,比如图 hugegraph 和 hugegraph1,其中 hugegraph 以 
cassandra 作为后端,hugegraph1 以 rocksdb作为后端。
+我们的系统是可以存在多个图的,并且各个图的后端可以不一样,比如图 `hugegraph_rocksdb` 和 `hugegraph_mysql`,其中 
`hugegraph_rocksdb` 以 `RocksDB` 作为后端,`hugegraph_mysql` 以 `MySQL` 作为后端。
 
 配置方法也很简单:
 
-**修改 gremlin-server.yaml**
-
-在 gremlin-server.yaml 的 graphs 域中添加一个键值对,键为图的名字,值为图的配置文件路径,比如:
-
-```yaml
-graphs: {
-  hugegraph: conf/hugegraph.properties,
-  hugegraph1: conf/hugegraph1.properties
-}
-```
-
 **修改 rest-server.properties**
 
-在 rest-server.properties 的 graphs 域中添加一个键值对,键为图的名字,值为图的配置文件路径,比如:
+在 rest-server.properties 的 graphs 域中修改图的配置文件路径(默认路径),比如:
 
 ```properties
-graphs=[hugegraph:conf/hugegraph.properties, 
hugegraph1:conf/hugegraph1.properties]
+graphs=./conf/graphs
 ```
 
-**添加 hugegraph1.properties**
+在 `conf/graphs` 路径下基于 `hugegraph.properties` 修改得到 
`hugegraph_mysql_backend.properties` 和   `hugegraph_rocksdb_backend.properties`

Review Comment:
   这里主要是区分下 `properties` 文件名和配置的 `store` 
名称,下面的查询语句也体现了查询graphs得到的是内部存储的图名称(store字段的),但是查询某个图的信息用的是配置文件名称(eg: 
`hugegraph_mysql_backend`) 😃 
   
   查看创建的图:
   
   ```bash
   curl http://127.0.0.1:8080/graphs/
   {"graphs":["hugegraph_rocksdb","hugegraph_mysql"]}
   ```
   
   查看某个图的信息:
   
   ```bash
   curl http://127.0.0.1:8080/graphs/hugegraph_mysql_backend
   {"name":"hugegraph_mysql","backend":"mysql"}
   ```



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