This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-hugegraph-doc.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 74708fe3 Update faq.md (#223)
74708fe3 is described below

commit 74708fe30886762f261112103c25c2b6f0dd8ea4
Author: imbajin <[email protected]>
AuthorDate: Sun May 14 12:29:25 2023 +0000

    Update faq.md (#223)
    
    update project url link
    
    ---------
    
    Co-authored-by: imbajin <[email protected]> 
ecb96905914a734dab9d0daad50d32acd545c09e
---
 docs/_print/index.html        | 22 +++++------
 docs/guides/_print/index.html | 22 +++++------
 docs/guides/faq/index.html    | 89 +++++++++++--------------------------------
 docs/guides/index.xml         | 88 +++++++++++++++++++++---------------------
 docs/index.xml                | 88 +++++++++++++++++++++---------------------
 en/index.html                 |  2 +-
 en/sitemap.xml                |  2 +-
 sitemap.xml                   |  2 +-
 8 files changed, 135 insertions(+), 180 deletions(-)

diff --git a/docs/_print/index.html b/docs/_print/index.html
index 954e718f..330d0eff 100644
--- a/docs/_print/index.html
+++ b/docs/_print/index.html
@@ -6505,17 +6505,17 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 </span></span></code></pre></div><h6 id=response-body-1>Response Body</h6><div 
class=highlight><pre tabindex=0 
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code 
class=language-json data-lang=json><span style=display:flex><span><span 
style=color:#000;font-weight:700>{</span>
 </span></span><span style=display:flex><span>    <span 
style=color:#204a87;font-weight:700>&#34;mode&#34;</span><span 
style=color:#000;font-weight:700>:</span> <span 
style=color:#4e9a06>&#34;RESTORING&#34;</span>
 </span></span><span style=display:flex><span><span 
style=color:#000;font-weight:700>}</span>
-</span></span></code></pre></div></div><div class=td-content 
style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>6.5 - 
FAQ</h1><ul><li><p>如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 
Mysql?</p><p>根据你的具体需要来判断, 一般单机或数据量 &lt; 100 亿推荐 RocksDB, 
其他推荐使用分布式存储的后端集群</p></li><li><p>启动服务时提示:<code>xxx (core dumped) 
xxx</code></p><p>请检查 JDK 版本是否为 Java 11, 至少要求是 Java 
8</p></li><li><p>启动服务成功了,但是操作图时有类似于"无法连接到后端或连接未打开"的提示</p><p>第一次启动服务前,需要先使用<code>init-store</code>初始化后端,后续版本会将提示得更清晰
 [...]
-</span></span><span style=display:flex><span>--------| ----
-</span></span><span style=display:flex><span>+       | %2B
-</span></span><span style=display:flex><span>空格     | %20
-</span></span><span style=display:flex><span>/       | %2F
-</span></span><span style=display:flex><span>?       | %3F
-</span></span><span style=display:flex><span>%       | %25
-</span></span><span style=display:flex><span>#       | %23
-</span></span><span style=display:flex><span>&amp;       | %26
-</span></span><span style=display:flex><span>=       | %3D
-</span></span></code></pre></div></li><li><p>查询某一类别的顶点或边(<code>query by 
label</code>)时提示超时</p><p>由于属于某一label的数据量可能比较多,请加上limit限制。</p></li><li><p>通过<code>RESTful
 API</code>操作图是可以的,但是发送<code>Gremlin</code>语句就报错:<code>Request 
Failed(500)</code></p><p>可能是<code>GremlinServer</code>的配置有误,检查<code>gremlin-server.yaml</code>的<code>host</code>、<code>port</code>是否与<code>rest-server.properties</code>的<code>gremlinserver.url</code>匹配,如不匹配则修改,然后重启服务。</p></li><li><p>使用<code>Loader</code>导数据出现<code>Sock
 [...]
+</span></span></code></pre></div></div><div class=td-content 
style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>6.5 - 
FAQ</h1><ul><li><p>How to choose the back-end storage? Choose RocksDB or 
Cassandra or Hbase or Mysql?</p><p>Judge according to your specific needs. 
Generally, if the stand-alone machine or the data volume is &lt; 10 billion, 
RocksDB is recommended, and other back-end clusters that use distributed 
storage are recommended.</p></li><li><p>Prompt when s [...]
+</span></span><span style=display:flex><span>------------------| -------------
+</span></span><span style=display:flex><span>+                 | %2B
+</span></span><span style=display:flex><span>space             | %20
+</span></span><span style=display:flex><span>/                 | %2F
+</span></span><span style=display:flex><span>?                 | %3F
+</span></span><span style=display:flex><span>%                 | %25
+</span></span><span style=display:flex><span>#                 | %23
+</span></span><span style=display:flex><span>&amp;                 | %26
+</span></span><span style=display:flex><span>=                 | %3D
+</span></span></code></pre></div></li><li><p>Timeout when querying vertices or 
edges of a certain category (<code>query by label</code>)</p><p>Since the 
amount of data belonging to a certain label may be relatively large, please add 
a limit limit.</p></li><li><p>It is possible to operate the graph through the 
<code>RESTful API</code>, but when sending <code>Gremlin</code> statements, an 
error is reported: <code>Request Failed(500)</code></p><p>It may be that the 
configuration of <code>Gr [...]
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span><span 
style=color:#000>schema</span><span 
style=color:#ce5c00;font-weight:700>.</span><span 
style=color:#c4a000>propertyKey</span><span 
style=color:#ce5c00;font-weight:700>(</span><span 
style=color:#4e9a06>&#34;name&#34;</span><span 
style=color:#ce5c00;font-weight:700>).</span><span 
style=color:#c4a000>asText</span><span 
style=color:#ce5c00;font-weight:700>().</span><span 
style=color:#c4a000>ifNotExist</span><span style=color:#ce5c00;font-weig [...]
 </span></span><span style=display:flex><span><span 
style=color:#000>schema</span><span 
style=color:#ce5c00;font-weight:700>.</span><span 
style=color:#c4a000>propertyKey</span><span 
style=color:#ce5c00;font-weight:700>(</span><span 
style=color:#4e9a06>&#34;age&#34;</span><span 
style=color:#ce5c00;font-weight:700>).</span><span 
style=color:#c4a000>asInt</span><span 
style=color:#ce5c00;font-weight:700>().</span><span 
style=color:#c4a000>ifNotExist</span><span style=color:#ce5c00;font-weight [...]
diff --git a/docs/guides/_print/index.html b/docs/guides/_print/index.html
index 1dda7009..11b67ead 100644
--- a/docs/guides/_print/index.html
+++ b/docs/guides/_print/index.html
@@ -305,17 +305,17 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 </span></span></code></pre></div><h6 id=response-body-1>Response Body</h6><div 
class=highlight><pre tabindex=0 
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code 
class=language-json data-lang=json><span style=display:flex><span><span 
style=color:#000;font-weight:700>{</span>
 </span></span><span style=display:flex><span>    <span 
style=color:#204a87;font-weight:700>&#34;mode&#34;</span><span 
style=color:#000;font-weight:700>:</span> <span 
style=color:#4e9a06>&#34;RESTORING&#34;</span>
 </span></span><span style=display:flex><span><span 
style=color:#000;font-weight:700>}</span>
-</span></span></code></pre></div></div><div class=td-content 
style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>5 - 
FAQ</h1><ul><li><p>如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 
Mysql?</p><p>根据你的具体需要来判断, 一般单机或数据量 &lt; 100 亿推荐 RocksDB, 
其他推荐使用分布式存储的后端集群</p></li><li><p>启动服务时提示:<code>xxx (core dumped) 
xxx</code></p><p>请检查 JDK 版本是否为 Java 11, 至少要求是 Java 
8</p></li><li><p>启动服务成功了,但是操作图时有类似于"无法连接到后端或连接未打开"的提示</p><p>第一次启动服务前,需要先使用<code>init-store</code>初始化后端,后续版本会将提示得更清晰直接
 [...]
-</span></span><span style=display:flex><span>--------| ----
-</span></span><span style=display:flex><span>+       | %2B
-</span></span><span style=display:flex><span>空格     | %20
-</span></span><span style=display:flex><span>/       | %2F
-</span></span><span style=display:flex><span>?       | %3F
-</span></span><span style=display:flex><span>%       | %25
-</span></span><span style=display:flex><span>#       | %23
-</span></span><span style=display:flex><span>&amp;       | %26
-</span></span><span style=display:flex><span>=       | %3D
-</span></span></code></pre></div></li><li><p>查询某一类别的顶点或边(<code>query by 
label</code>)时提示超时</p><p>由于属于某一label的数据量可能比较多,请加上limit限制。</p></li><li><p>通过<code>RESTful
 API</code>操作图是可以的,但是发送<code>Gremlin</code>语句就报错:<code>Request 
Failed(500)</code></p><p>可能是<code>GremlinServer</code>的配置有误,检查<code>gremlin-server.yaml</code>的<code>host</code>、<code>port</code>是否与<code>rest-server.properties</code>的<code>gremlinserver.url</code>匹配,如不匹配则修改,然后重启服务。</p></li><li><p>使用<code>Loader</code>导数据出现<code>Sock
 [...]
+</span></span></code></pre></div></div><div class=td-content 
style=page-break-before:always><h1 id=pg-3465b699399f48689cdc6b5e59a10d69>5 - 
FAQ</h1><ul><li><p>How to choose the back-end storage? Choose RocksDB or 
Cassandra or Hbase or Mysql?</p><p>Judge according to your specific needs. 
Generally, if the stand-alone machine or the data volume is &lt; 10 billion, 
RocksDB is recommended, and other back-end clusters that use distributed 
storage are recommended.</p></li><li><p>Prompt when sta [...]
+</span></span><span style=display:flex><span>------------------| -------------
+</span></span><span style=display:flex><span>+                 | %2B
+</span></span><span style=display:flex><span>space             | %20
+</span></span><span style=display:flex><span>/                 | %2F
+</span></span><span style=display:flex><span>?                 | %3F
+</span></span><span style=display:flex><span>%                 | %25
+</span></span><span style=display:flex><span>#                 | %23
+</span></span><span style=display:flex><span>&amp;                 | %26
+</span></span><span style=display:flex><span>=                 | %3D
+</span></span></code></pre></div></li><li><p>Timeout when querying vertices or 
edges of a certain category (<code>query by label</code>)</p><p>Since the 
amount of data belonging to a certain label may be relatively large, please add 
a limit limit.</p></li><li><p>It is possible to operate the graph through the 
<code>RESTful API</code>, but when sending <code>Gremlin</code> statements, an 
error is reported: <code>Request Failed(500)</code></p><p>It may be that the 
configuration of <code>Gr [...]
 <script 
src=https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.min.js 
integrity="sha512-UR25UO94eTnCVwjbXozyeVd6ZqpaAE9naiEUBK/A+QDbfSTQFhPGj5lOR6d8tsgbBk84Ggb5A3EkjsOgPRPcKA=="
 crossorigin=anonymous></script>
 <script src=/js/tabpane-persist.js></script>
 <script 
src=/js/main.min.aa9f4c5dae6a98b2c46277f4c56f1673a2b000d1756ce4ffae93784cab25e6d5.js
 integrity="sha256-qp9MXa5qmLLEYnf0xW8Wc6KwANF1bOT/rpN4TKsl5tU=" 
crossorigin=anonymous></script>
diff --git a/docs/guides/faq/index.html b/docs/guides/faq/index.html
index 689ce040..c953ad0b 100644
--- a/docs/guides/faq/index.html
+++ b/docs/guides/faq/index.html
@@ -1,77 +1,32 @@
 <!doctype html><html lang=en class=no-js><head><meta charset=utf-8><meta 
name=viewport 
content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta 
name=generator content="Hugo 0.102.3"><meta name=robots content="index, 
follow"><link rel="shortcut icon" href=/favicons/favicon.ico><link 
rel=apple-touch-icon href=/favicons/apple-touch-icon-180x180.png 
sizes=180x180><link rel=icon type=image/png href=/favicons/favicon-16x16.png 
sizes=16x16><link rel=icon type=image/png href=/favicons [...]
 
-如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 Mysql?
-根据你的具体需要来判断, 一般单机或数据量 < 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群
-
-
-启动服务时提示:xxx (core dumped) xxx …"><meta property="og:title" content="FAQ"><meta 
property="og:description" content="如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 
Mysql?
-根据你的具体需要来判断, 一般单机或数据量 < 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群
-启动服务时提示:xxx (core dumped) xxx
-请检查 JDK 版本是否为 Java 11, 至少要求是 Java 8
-启动服务成功了,但是操作图时有类似于&#34;无法连接到后端或连接未打开&#34;的提示
-第一次启动服务前,需要先使用init-store初始化后端,后续版本会将提示得更清晰直接。
-所有的后端在使用前都需要执行init-store吗,序列化的选择可以随意填写么?
-除了memory不需要,其他后端均需要,如:cassandra、hbase和rocksdb等,序列化需一一对应不可随意填写。
-执行init-store报错:Exception in thread &#34;main&#34; 
java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni3226083071221514754.so: 
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)
-RocksDB需要 gcc 4.3.0 (GLIBCXX_3.4.10) 及以上版本
-执行init-store.sh时报错:NoHostAvailableException
-NoHostAvailableException 
是指无法连接到Cassandra服务,如果确定是要使用cassandra后端,请先安装并启动这个服务。至于这个提示本身可能不够直白,我们会更新到文档进行说明的。
-bin目录下包含start-hugegraph.sh、start-restserver.sh和start-gremlinserver.sh三个似乎与启动有关的脚本,到底该使用哪个
-自0.3.3版本以来,已经把 GremlinServer 和 RestServer 合并为 HugeGraphServer 
了,使用start-hugegraph.sh启动即可,后两个在后续版本会被删掉。
-配置了两个图,名字是hugegraph和hugegraph1,而启动服务的命令是start-hugegraph.sh,是只打开了hugegraph这个图吗
-start-hugegraph.sh会打开所有gremlin-server.yaml的graphs下的图,这二者并无名字上的直接关系
-服务启动成功后,使用curl查询所有顶点时返回乱码
-服务端返回的批量顶点/边是压缩(gzip)过的,可以使用管道重定向至 gunzip 进行解压(curl http://example | 
gunzip),也可以用Firefox的postman或者Chrome浏览器的restlet插件发请求,会自动解压缩响应数据。"><meta 
property="og:type" content="article"><meta property="og:url" 
content="/docs/guides/faq/"><meta property="article:section" 
content="docs"><meta property="article:modified_time" 
content="2023-01-01T16:16:43+08:00"><meta property="og:site_name" 
content="HugeGraph"><meta itemprop=name content="FAQ"><meta 
itemprop=description content="如何选择后端存储? 选 RocksDB  [...]
-根据你的具体需要来判断, 一般单机或数据量 < 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群
-启动服务时提示:xxx (core dumped) xxx
-请检查 JDK 版本是否为 Java 11, 至少要求是 Java 8
-启动服务成功了,但是操作图时有类似于&#34;无法连接到后端或连接未打开&#34;的提示
-第一次启动服务前,需要先使用init-store初始化后端,后续版本会将提示得更清晰直接。
-所有的后端在使用前都需要执行init-store吗,序列化的选择可以随意填写么?
-除了memory不需要,其他后端均需要,如:cassandra、hbase和rocksdb等,序列化需一一对应不可随意填写。
-执行init-store报错:Exception in thread &#34;main&#34; 
java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni3226083071221514754.so: 
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)
-RocksDB需要 gcc 4.3.0 (GLIBCXX_3.4.10) 及以上版本
-执行init-store.sh时报错:NoHostAvailableException
-NoHostAvailableException 
是指无法连接到Cassandra服务,如果确定是要使用cassandra后端,请先安装并启动这个服务。至于这个提示本身可能不够直白,我们会更新到文档进行说明的。
-bin目录下包含start-hugegraph.sh、start-restserver.sh和start-gremlinserver.sh三个似乎与启动有关的脚本,到底该使用哪个
-自0.3.3版本以来,已经把 GremlinServer 和 RestServer 合并为 HugeGraphServer 
了,使用start-hugegraph.sh启动即可,后两个在后续版本会被删掉。
-配置了两个图,名字是hugegraph和hugegraph1,而启动服务的命令是start-hugegraph.sh,是只打开了hugegraph这个图吗
-start-hugegraph.sh会打开所有gremlin-server.yaml的graphs下的图,这二者并无名字上的直接关系
-服务启动成功后,使用curl查询所有顶点时返回乱码
-服务端返回的批量顶点/边是压缩(gzip)过的,可以使用管道重定向至 gunzip 进行解压(curl http://example | 
gunzip),也可以用Firefox的postman或者Chrome浏览器的restlet插件发请求,会自动解压缩响应数据。"><meta 
itemprop=dateModified content="2023-01-01T16:16:43+08:00"><meta 
itemprop=wordCount content="169"><meta itemprop=keywords content><meta 
name=twitter:card content="summary"><meta name=twitter:title 
content="FAQ"><meta name=twitter:description content="如何选择后端存储? 选 RocksDB 还是 
Cassandra 还是 Hbase 还是 Mysql?
-根据你的具体需要来判断, 一般单机或数据量 < 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群
-启动服务时提示:xxx (core dumped) xxx
-请检查 JDK 版本是否为 Java 11, 至少要求是 Java 8
-启动服务成功了,但是操作图时有类似于&#34;无法连接到后端或连接未打开&#34;的提示
-第一次启动服务前,需要先使用init-store初始化后端,后续版本会将提示得更清晰直接。
-所有的后端在使用前都需要执行init-store吗,序列化的选择可以随意填写么?
-除了memory不需要,其他后端均需要,如:cassandra、hbase和rocksdb等,序列化需一一对应不可随意填写。
-执行init-store报错:Exception in thread &#34;main&#34; 
java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni3226083071221514754.so: 
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)
-RocksDB需要 gcc 4.3.0 (GLIBCXX_3.4.10) 及以上版本
-执行init-store.sh时报错:NoHostAvailableException
-NoHostAvailableException 
是指无法连接到Cassandra服务,如果确定是要使用cassandra后端,请先安装并启动这个服务。至于这个提示本身可能不够直白,我们会更新到文档进行说明的。
-bin目录下包含start-hugegraph.sh、start-restserver.sh和start-gremlinserver.sh三个似乎与启动有关的脚本,到底该使用哪个
-自0.3.3版本以来,已经把 GremlinServer 和 RestServer 合并为 HugeGraphServer 
了,使用start-hugegraph.sh启动即可,后两个在后续版本会被删掉。
-配置了两个图,名字是hugegraph和hugegraph1,而启动服务的命令是start-hugegraph.sh,是只打开了hugegraph这个图吗
-start-hugegraph.sh会打开所有gremlin-server.yaml的graphs下的图,这二者并无名字上的直接关系
-服务启动成功后,使用curl查询所有顶点时返回乱码
-服务端返回的批量顶点/边是压缩(gzip)过的,可以使用管道重定向至 gunzip 进行解压(curl http://example | 
gunzip),也可以用Firefox的postman或者Chrome浏览器的restlet插件发请求,会自动解压缩响应数据。"><link 
rel=preload 
href=/scss/main.min.ad1b0560bef9c54394313a5bc50d3313d4e56ea590ddc5cfb84a077dfc6fec5e.css
 as=style><link 
href=/scss/main.min.ad1b0560bef9c54394313a5bc50d3313d4e56ea590ddc5cfb84a077dfc6fec5e.css
 rel=stylesheet integrity><script 
src=https://code.jquery.com/jquery-3.5.1.min.js 
integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" cr [...]
+How to choose the back-end storage? Choose RocksDB or Cassandra or Hbase or 
Mysql?
+Judge according to your specific needs. Generally, if the …"><meta 
property="og:title" content="FAQ"><meta property="og:description" content="How 
to choose the back-end storage? Choose RocksDB or Cassandra or Hbase or Mysql?
+Judge according to your specific needs. Generally, if the stand-alone machine 
or the data volume is < 10 billion, RocksDB is recommended, and other back-end 
clusters that use distributed storage are recommended.
+Prompt when starting the service: xxx (core dumped) xxx
+Please check if the JDK version is Java 11, at least Java 8 is required"><meta 
property="og:type" content="article"><meta property="og:url" 
content="/docs/guides/faq/"><meta property="article:section" 
content="docs"><meta property="article:modified_time" 
content="2023-05-14T07:28:41-05:00"><meta property="og:site_name" 
content="HugeGraph"><meta itemprop=name content="FAQ"><meta 
itemprop=description content="How to choose the back-end storage? Choose 
RocksDB or Cassandra or Hbase or Mysql?
+Judge according to your specific needs. Generally, if the stand-alone machine 
or the data volume is < 10 billion, RocksDB is recommended, and other back-end 
clusters that use distributed storage are recommended.
+Prompt when starting the service: xxx (core dumped) xxx
+Please check if the JDK version is Java 11, at least Java 8 is required"><meta 
itemprop=dateModified content="2023-05-14T07:28:41-05:00"><meta 
itemprop=wordCount content="1032"><meta itemprop=keywords content><meta 
name=twitter:card content="summary"><meta name=twitter:title 
content="FAQ"><meta name=twitter:description content="How to choose the 
back-end storage? Choose RocksDB or Cassandra or Hbase or Mysql?
+Judge according to your specific needs. Generally, if the stand-alone machine 
or the data volume is < 10 billion, RocksDB is recommended, and other back-end 
clusters that use distributed storage are recommended.
+Prompt when starting the service: xxx (core dumped) xxx
+Please check if the JDK version is Java 11, at least Java 8 is required"><link 
rel=preload 
href=/scss/main.min.ad1b0560bef9c54394313a5bc50d3313d4e56ea590ddc5cfb84a077dfc6fec5e.css
 as=style><link 
href=/scss/main.min.ad1b0560bef9c54394313a5bc50d3313d4e56ea590ddc5cfb84a077dfc6fec5e.css
 rel=stylesheet integrity><script 
src=https://code.jquery.com/jquery-3.5.1.min.js 
integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" 
crossorigin=anonymous></script>
 <link rel=stylesheet href=/css/prism.css><script 
type=application/javascript>var 
doNotTrack=!1;doNotTrack||(window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)},ga.l=+new
 
Date,ga("create","UA-00000000-0","auto"),ga("send","pageview"))</script><script 
async src=https://www.google-analytics.com/analytics.js></script></head><body 
class=td-page><header><nav class="js-navbar-scroll navbar navbar-expand 
navbar-dark flex-column flex-md-row td-navbar"><a class=navbar-brand href=/><sp 
[...]
 <a 
href=https://github.com/apache/incubator-hugegraph-doc/edit/master/content/en/docs/guides/faq.md
 class=td-page-meta--edit target=_blank rel=noopener><i class="fa fa-edit 
fa-fw"></i> Edit this page</a>
 <a 
href="https://github.com/apache/incubator-hugegraph-doc/new/master/content/en/docs/guides/faq.md?filename=change-me.md&value=---%0Atitle%3A+%22Long+Page+Title%22%0AlinkTitle%3A+%22Short+Nav+Title%22%0Aweight%3A+100%0Adescription%3A+%3E-%0A+++++Page+description+for+heading+and+indexes.%0A---%0A%0A%23%23+Heading%0A%0AEdit+this+template+to+create+your+new+page.%0A%0A%2A+Give+it+a+good+name%2C+ending+in+%60.md%60+-+e.g.+%60getting-started.md%60%0A%2A+Edit+the+%22front+matter%22+section+at
 [...]
 <a 
href="https://github.com/apache/incubator-hugegraph-doc/issues/new?title=FAQ"; 
class=td-page-meta--issue target=_blank rel=noopener><i class="fab fa-github 
fa-fw"></i> Create documentation issue</a>
 <a href=https://github.com/apache/incubator-hugegraph/issues/new 
class=td-page-meta--project-issue target=_blank rel=noopener><i class="fas 
fa-tasks fa-fw"></i> Create project issue</a>
-<a id=print href=/docs/guides/_print/><i class="fa fa-print fa-fw"></i> Print 
entire section</a></div></aside><main class="col-12 col-md-9 col-xl-8 pl-md-5" 
role=main><nav aria-label=breadcrumb class=td-breadcrumbs><ol 
class=breadcrumb><li class=breadcrumb-item><a 
href=/docs/>Documentation</a></li><li class=breadcrumb-item><a 
href=/docs/guides/>GUIDES</a></li><li class="breadcrumb-item active" 
aria-current=page><a href=/docs/guides/faq/>FAQ</a></li></ol></nav><div 
class=td-content><h1>FA [...]
-</span></span><span style=display:flex><span>--------| ----
-</span></span><span style=display:flex><span>+       | %2B
-</span></span><span style=display:flex><span>空格     | %20
-</span></span><span style=display:flex><span>/       | %2F
-</span></span><span style=display:flex><span>?       | %3F
-</span></span><span style=display:flex><span>%       | %25
-</span></span><span style=display:flex><span>#       | %23
-</span></span><span style=display:flex><span>&amp;       | %26
-</span></span><span style=display:flex><span>=       | %3D
-</span></span></code></pre></div></li><li><p>查询某一类别的顶点或边(<code>query by 
label</code>)时提示超时</p><p>由于属于某一label的数据量可能比较多,请加上limit限制。</p></li><li><p>通过<code>RESTful
 API</code>操作图是可以的,但是发送<code>Gremlin</code>语句就报错:<code>Request 
Failed(500)</code></p><p>可能是<code>GremlinServer</code>的配置有误,检查<code>gremlin-server.yaml</code>的<code>host</code>、<code>port</code>是否与<code>rest-server.properties</code>的<code>gremlinserver.url</code>匹配,如不匹配则修改,然后重启服务。</p></li><li><p>使用<code>Loader</code>导数据出现<code>Sock
 [...]
+<a id=print href=/docs/guides/_print/><i class="fa fa-print fa-fw"></i> Print 
entire section</a></div></aside><main class="col-12 col-md-9 col-xl-8 pl-md-5" 
role=main><nav aria-label=breadcrumb class=td-breadcrumbs><ol 
class=breadcrumb><li class=breadcrumb-item><a 
href=/docs/>Documentation</a></li><li class=breadcrumb-item><a 
href=/docs/guides/>GUIDES</a></li><li class="breadcrumb-item active" 
aria-current=page><a href=/docs/guides/faq/>FAQ</a></li></ol></nav><div 
class=td-content><h1>FA [...]
+</span></span><span style=display:flex><span>------------------| -------------
+</span></span><span style=display:flex><span>+                 | %2B
+</span></span><span style=display:flex><span>space             | %20
+</span></span><span style=display:flex><span>/                 | %2F
+</span></span><span style=display:flex><span>?                 | %3F
+</span></span><span style=display:flex><span>%                 | %25
+</span></span><span style=display:flex><span>#                 | %23
+</span></span><span style=display:flex><span>&amp;                 | %26
+</span></span><span style=display:flex><span>=                 | %3D
+</span></span></code></pre></div></li><li><p>Timeout when querying vertices or 
edges of a certain category (<code>query by label</code>)</p><p>Since the 
amount of data belonging to a certain label may be relatively large, please add 
a limit limit.</p></li><li><p>It is possible to operate the graph through the 
<code>RESTful API</code>, but when sending <code>Gremlin</code> statements, an 
error is reported: <code>Request Failed(500)</code></p><p>It may be that the 
configuration of <code>Gr [...]
 <script 
src=https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.min.js 
integrity="sha512-UR25UO94eTnCVwjbXozyeVd6ZqpaAE9naiEUBK/A+QDbfSTQFhPGj5lOR6d8tsgbBk84Ggb5A3EkjsOgPRPcKA=="
 crossorigin=anonymous></script>
 <script src=/js/tabpane-persist.js></script>
 <script 
src=/js/main.min.aa9f4c5dae6a98b2c46277f4c56f1673a2b000d1756ce4ffae93784cab25e6d5.js
 integrity="sha256-qp9MXa5qmLLEYnf0xW8Wc6KwANF1bOT/rpN4TKsl5tU=" 
crossorigin=anonymous></script>
diff --git a/docs/guides/index.xml b/docs/guides/index.xml
index 3015a03e..a7dfc693 100644
--- a/docs/guides/index.xml
+++ b/docs/guides/index.xml
@@ -578,52 +578,52 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div></description></item><item><title>Docs:
 FAQ</title><link>/docs/guides/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 
+0000</pubDate><guid>/docs/guides/faq/</guid><description>
 &lt;ul>
 &lt;li>
-&lt;p>如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 Mysql?&lt;/p>
-&lt;p>根据你的具体需要来判断, 一般单机或数据量 &amp;lt; 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群&lt;/p>
+&lt;p>How to choose the back-end storage? Choose RocksDB or Cassandra or Hbase 
or Mysql?&lt;/p>
+&lt;p>Judge according to your specific needs. Generally, if the stand-alone 
machine or the data volume is &amp;lt; 10 billion, RocksDB is recommended, and 
other back-end clusters that use distributed storage are recommended.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>启动服务时提示:&lt;code>xxx (core dumped) xxx&lt;/code>&lt;/p>
-&lt;p>请检查 JDK 版本是否为 Java 11, 至少要求是 Java 8&lt;/p>
+&lt;p>Prompt when starting the service: &lt;code>xxx (core dumped) 
xxx&lt;/code>&lt;/p>
+&lt;p>Please check if the JDK version is Java 11, at least Java 8 is 
required&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>启动服务成功了,但是操作图时有类似于&amp;quot;无法连接到后端或连接未打开&amp;quot;的提示&lt;/p>
-&lt;p>第一次启动服务前,需要先使用&lt;code>init-store&lt;/code>初始化后端,后续版本会将提示得更清晰直接。&lt;/p>
+&lt;p>The service is started successfully, but there is a prompt similar to 
&amp;ldquo;Unable to connect to the backend or the connection is not 
open&amp;rdquo; when operating the graph&lt;/p>
+&lt;p>init-storeBefore starting the service for the first time, you need to 
use the initialization backend first , and subsequent versions will prompt more 
clearly and directly.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>所有的后端在使用前都需要执行&lt;code>init-store&lt;/code>吗,序列化的选择可以随意填写么?&lt;/p>
-&lt;p>除了&lt;code>memory&lt;/code>不需要,其他后端均需要,如:&lt;code>cassandra&lt;/code>、&lt;code>hbase&lt;/code>和&lt;code>rocksdb&lt;/code>等,序列化需一一对应不可随意填写。&lt;/p>
+&lt;p>Do all backends need to be executed before use init-store, and can the 
serialization options be filled in at will?&lt;/p>
+&lt;p>Except memorynot required, other backends are required, such as: 
&lt;code>cassandra&lt;/code>, &lt;code>hbaseand&lt;/code>, 
&lt;code>rocksdb&lt;/code>, etc. Serialization needs to be one-to-one 
correspondence and cannot be filled in at will.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>执行&lt;code>init-store&lt;/code>报错:&lt;code>Exception in thread 
&amp;quot;main&amp;quot; java.lang.UnsatisfiedLinkError: 
/tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version 
`GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)&lt;/code>&lt;/p>
-&lt;p>RocksDB需要 gcc 4.3.0 (GLIBCXX_3.4.10) 及以上版本&lt;/p>
+&lt;p>Execution &lt;code>init-store&lt;/code> error: &lt;code>Exception in 
thread &amp;quot;main&amp;quot; java.lang.UnsatisfiedLinkError: 
/tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version 
`GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)&lt;/code>&lt;/p>
+&lt;p>RocksDB requires gcc 4.3.0 (GLIBCXX_3.4.10) and above&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>执行&lt;code>init-store.sh&lt;/code>时报错:&lt;code>NoHostAvailableException&lt;/code>&lt;/p>
-&lt;p>&lt;code>NoHostAvailableException&lt;/code> 
是指无法连接到&lt;code>Cassandra&lt;/code>服务,如果确定是要使用&lt;code>cassandra&lt;/code>后端,请先安装并启动这个服务。至于这个提示本身可能不够直白,我们会更新到文档进行说明的。&lt;/p>
+&lt;p>The error &lt;code>NoHostAvailableException&lt;/code> occurred while 
executing &lt;code>init-store.sh&lt;/code>.&lt;/p>
+&lt;p>&lt;code>NoHostAvailableException&lt;/code> means that the 
&lt;code>Cassandra&lt;/code> service cannot be connected to. If you are sure 
that you want to use the Cassandra backend, please install and start this 
service first. As for the message itself, it may not be clear enough, and we 
will update the documentation to provide further explanation.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>&lt;code>bin&lt;/code>目录下包含&lt;code>start-hugegraph.sh&lt;/code>、&lt;code>start-restserver.sh&lt;/code>和&lt;code>start-gremlinserver.sh&lt;/code>三个似乎与启动有关的脚本,到底该使用哪个&lt;/p>
-&lt;p>自0.3.3版本以来,已经把 GremlinServer 和 RestServer 合并为 HugeGraphServer 
了,使用&lt;code>start-hugegraph.sh&lt;/code>启动即可,后两个在后续版本会被删掉。&lt;/p>
+&lt;p>The &lt;code>bin&lt;/code> directory contains 
&lt;code>start-hugegraph.sh&lt;/code>, &lt;code>start-restserver.sh&lt;/code> 
and &lt;code>start-gremlinserver.sh&lt;/code>. These scripts seem to be related 
to startup. Which one should be used?&lt;/p>
+&lt;p>Since version 0.3.3, GremlinServer and RestServer have been merged into 
HugeGraphServer. To start, use start-hugegraph.sh. The latter two will be 
removed in future versions.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>配置了两个图,名字是&lt;code>hugegraph&lt;/code>和&lt;code>hugegraph1&lt;/code>,而启动服务的命令是&lt;code>start-hugegraph.sh&lt;/code>,是只打开了&lt;code>hugegraph&lt;/code>这个图吗&lt;/p>
-&lt;p>&lt;code>start-hugegraph.sh&lt;/code>会打开所有&lt;code>gremlin-server.yaml&lt;/code>的&lt;code>graphs&lt;/code>下的图,这二者并无名字上的直接关系&lt;/p>
+&lt;p>Two graphs are configured, the names are &lt;code>hugegraph&lt;/code> 
and &lt;code>hugegraph1&lt;/code>, and the command to start the service is 
&lt;code>start-hugegraph.sh&lt;/code>. Is only the hugegraph graph 
opened?&lt;/p>
+&lt;p>&lt;code>start-hugegraph.sh&lt;/code> will open all graphs under the 
graphs of &lt;code>gremlin-server.yaml&lt;/code>. The two have no direct 
relationship in name&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>服务启动成功后,使用&lt;code>curl&lt;/code>查询所有顶点时返回乱码&lt;/p>
-&lt;p>服务端返回的批量顶点/边是压缩(gzip)过的,可以使用管道重定向至 &lt;code>gunzip&lt;/code> 
进行解压(&lt;code>curl http://example | 
gunzip&lt;/code>),也可以用&lt;code>Firefox&lt;/code>的&lt;code>postman&lt;/code>或者&lt;code>Chrome&lt;/code>浏览器的&lt;code>restlet&lt;/code>插件发请求,会自动解压缩响应数据。&lt;/p>
+&lt;p>After the service starts successfully, garbled characters are returned 
when using &lt;code>curl&lt;/code> to query all vertices&lt;/p>
+&lt;p>The batch vertices/edges returned by the server are compressed (gzip), 
and can be redirected to &lt;code>gunzip&lt;/code> for decompression 
(&lt;code>curl http://example | gunzip&lt;/code>), or can be sent with the 
&lt;code>postman&lt;/code> of &lt;code>Firefox&lt;/code> or the 
&lt;code>restlet&lt;/code> plug-in of Chrome browser. request, the response 
data will be decompressed automatically.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>使用顶点Id通过&lt;code>RESTful API&lt;/code>查询顶点时返回空,但是顶点确实是存在的&lt;/p>
-&lt;p>检查顶点Id的类型,如果是字符串类型,&lt;code>API&lt;/code>的&lt;code>url&lt;/code>中的id部分需要加上双引号,数字类型则不用加。&lt;/p>
+&lt;p>When using the vertex Id to query the vertex through the 
&lt;code>RESTful API&lt;/code>, it returns empty, but the vertex does 
exist&lt;/p>
+&lt;p>Check the type of the vertex ID. If it is a string type, the 
&amp;ldquo;id&amp;rdquo; part of the API URL needs to be enclosed in double 
quotes, while for numeric types, it is not necessary to enclose the ID in 
quotes.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>已经根据需要给顶点Id加上了双引号,但是通过&lt;code>RESTful API&lt;/code>查询顶点时仍然返回空&lt;/p>
-&lt;p>检查顶点id中是否包含&lt;code>+&lt;/code>、&lt;code>空格&lt;/code>、&lt;code>/&lt;/code>、&lt;code>?&lt;/code>、&lt;code>%&lt;/code>、&lt;code>&amp;amp;&lt;/code>和&lt;code>=&lt;/code>这些URL的保留字符,如果存在则需要进行编码。下表给出了编码值:&lt;/p>
-&lt;div class="highlight">&lt;pre tabindex="0" 
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code
 class="language-fallback" data-lang="fallback">&lt;span 
style="display:flex;">&lt;span>特殊字符 | 编码值
-&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>--------| ----
+&lt;p>Vertex Id has been double quoted as required, but querying the vertex 
via the RESTful API still returns empty&lt;/p>
+&lt;p>Check whether the vertex id contains &lt;code>+&lt;/code>, 
&lt;code>space&lt;/code>, &lt;code>/&lt;/code>, &lt;code>?&lt;/code>, 
&lt;code>%&lt;/code>, &lt;code>&amp;amp;&lt;/code>, and &lt;code>=&lt;/code> 
reserved characters of these &lt;code>URLs&lt;/code>. If they exist, they need 
to be encoded. The following table gives the coded values:&lt;/p>
+&lt;div class="highlight">&lt;pre tabindex="0" 
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code
 class="language-fallback" data-lang="fallback">&lt;span 
style="display:flex;">&lt;span>special character | encoded value
+&lt;/span>&lt;/span>&lt;span 
style="display:flex;">&lt;span>------------------| -------------
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>+ | %2B
-&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>空格 | %20
+&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>space | %20
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>/ | %2F
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>? | %3F
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>% | %25
@@ -632,40 +632,40 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>= | %3D
 &lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
 &lt;li>
-&lt;p>查询某一类别的顶点或边(&lt;code>query by label&lt;/code>)时提示超时&lt;/p>
-&lt;p>由于属于某一label的数据量可能比较多,请加上limit限制。&lt;/p>
+&lt;p>Timeout when querying vertices or edges of a certain category 
(&lt;code>query by label&lt;/code>)&lt;/p>
+&lt;p>Since the amount of data belonging to a certain label may be relatively 
large, please add a limit limit.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>通过&lt;code>RESTful 
API&lt;/code>操作图是可以的,但是发送&lt;code>Gremlin&lt;/code>语句就报错:&lt;code>Request 
Failed(500)&lt;/code>&lt;/p>
-&lt;p>可能是&lt;code>GremlinServer&lt;/code>的配置有误,检查&lt;code>gremlin-server.yaml&lt;/code>的&lt;code>host&lt;/code>、&lt;code>port&lt;/code>是否与&lt;code>rest-server.properties&lt;/code>的&lt;code>gremlinserver.url&lt;/code>匹配,如不匹配则修改,然后重启服务。&lt;/p>
+&lt;p>It is possible to operate the graph through the &lt;code>RESTful 
API&lt;/code>, but when sending &lt;code>Gremlin&lt;/code> statements, an error 
is reported: &lt;code>Request Failed(500)&lt;/code>&lt;/p>
+&lt;p>It may be that the configuration of &lt;code>GremlinServer&lt;/code> is 
wrong, check whether the &lt;code>host&lt;/code> and &lt;code>port&lt;/code> of 
&lt;code>gremlin-server.yaml&lt;/code> match the 
&lt;code>gremlinserver.url&lt;/code> of 
&lt;code>rest-server.properties&lt;/code>, if they do not match, modify them, 
and then Restart the service.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>使用&lt;code>Loader&lt;/code>导数据出现&lt;code>Socket 
Timeout&lt;/code>异常,然后导致&lt;code>Loader&lt;/code>中断&lt;/p>
-&lt;p>持续地导入数据会使&lt;code>Server&lt;/code>的压力过大,然后导致有些请求超时。可以通过调整&lt;code>Loader&lt;/code>的参数来适当缓解&lt;code>Server&lt;/code>压力(如:重试次数,重试间隔,错误容忍数等),降低该问题出现频率。&lt;/p>
+&lt;p>When using &lt;code>Loader&lt;/code> to import data, a &lt;code>Socket 
Timeout&lt;/code> exception occurs, and then &lt;code>Loader&lt;/code> is 
interrupted&lt;/p>
+&lt;p>Continuously importing data will put too much pressure on the 
&lt;code>Server&lt;/code>, which will cause some requests to time out. The 
pressure on &lt;code>Server&lt;/code> can be appropriately relieved by 
adjusting the parameters of &lt;code>Loader&lt;/code> (such as: number of 
retries, retry interval, error tolerance, etc.), and reduce the frequency of 
this problem.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>如何删除全部的顶点和边,RESTful 
API中没有这样的接口,调用&lt;code>gremlin&lt;/code>的&lt;code>g.V().drop()&lt;/code>会报错&lt;code>Vertices
 in transaction have reached capacity xxx&lt;/code>&lt;/p>
-&lt;p>目前确实没有好办法删除全部的数据,用户如果是自己部署的&lt;code>Server&lt;/code>和后端,可以直接清空数据库,重启&lt;code>Server&lt;/code>。可以使用paging
 API或scan API先获取所有数据,再逐条删除。&lt;/p>
+&lt;p>How to delete all vertices and edges. There is no such interface in the 
RESTful API. Calling &lt;code>g.V().drop()&lt;/code> of 
&lt;code>gremlin&lt;/code> will report an error &lt;code>Vertices in 
transaction have reached capacity xxx&lt;/code>&lt;/p>
+&lt;p>At present, there is really no good way to delete all the data. If the 
user deploys the &lt;code>Server&lt;/code> and the backend by himself, he can 
directly clear the database and restart the &lt;code>Server&lt;/code>. You can 
use the paging API or scan API to get all the data first, and then delete them 
one by one.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>清空了数据库,并且执行了&lt;code>init-store&lt;/code>,但是添加&lt;code>schema&lt;/code>时提示&amp;quot;xxx
 has existed&amp;quot;&lt;/p>
-&lt;p>&lt;code>HugeGraphServer&lt;/code>内是有缓存的,清空数据库的同时是需要重启&lt;code>Server&lt;/code>的,否则残留的缓存会产生不一致。&lt;/p>
+&lt;p>The database has been cleared and &lt;code>init-store&lt;/code> has been 
executed, but when trying to add a schema, the prompt &amp;ldquo;xxx has 
existed&amp;rdquo; appeared.&lt;/p>
+&lt;p>There is a cache in the &lt;code>HugeGraphServer&lt;/code>, and it is 
necessary to restart the &lt;code>Server&lt;/code> when the database is 
cleared, otherwise the residual cache will be inconsistent.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>插入顶点或边的过程中报错:&lt;code>Id max length is 128, but got xxx {yyy}&lt;/code> 
或 &lt;code>Big id max length is 32768, but got xxx&lt;/code>&lt;/p>
-&lt;p>为了保证查询性能,目前的后端存储对id列的长度做了限制,顶点id不能超过128字节,边id长度不能超过32768字节,索引id不能超过128字节。&lt;/p>
+&lt;p>An error is reported during the process of inserting vertices or edges: 
&lt;code>Id max length is 128, but got xxx {yyy}&lt;/code> or &lt;code>Big id 
max length is 32768, but got xxx&lt;/code>&lt;/p>
+&lt;p>In order to ensure query performance, the current backend storage limits 
the length of the id column. The vertex id cannot exceed 128 bytes, the edge id 
cannot exceed 32768 bytes, and the index id cannot exceed 128 bytes.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>是否支持嵌套属性,如果不支持,是否有什么替代方案&lt;/p>
-&lt;p>嵌套属性目前暂不支持。替代方案:可以把嵌套属性作为单独的顶点拿出来,然后用边连接起来。&lt;/p>
+&lt;p>Is there support for nested attributes, and if not, are there any 
alternatives?&lt;/p>
+&lt;p>Nested attributes are currently not supported. Alternative: Nested 
attributes can be taken out as individual vertices and connected with 
edges.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>一个&lt;code>EdgeLabel&lt;/code>是否可以连接多对&lt;code>VertexLabel&lt;/code>,比如&amp;quot;投资&amp;quot;关系,可以是&amp;quot;个人&amp;quot;投资&amp;quot;企业&amp;quot;,也可以是&amp;quot;企业&amp;quot;投资&amp;quot;企业&amp;quot;&lt;/p>
-&lt;p>一个&lt;code>EdgeLabel&lt;/code>不支持连接多对&lt;code>VertexLabel&lt;/code>,需要用户将&lt;code>EdgeLabel&lt;/code>拆分得更细一点,如:&amp;ldquo;个人投资&amp;rdquo;,&amp;ldquo;企业投资&amp;rdquo;。&lt;/p>
+&lt;p>Can an &lt;code>EdgeLabel&lt;/code> connect multiple pairs of 
&lt;code>VertexLabel&lt;/code>, such as &amp;ldquo;investment&amp;rdquo; 
relationship, which can be &amp;ldquo;individual&amp;rdquo; investing in 
&amp;ldquo;enterprise&amp;rdquo;, or &amp;ldquo;enterprise&amp;rdquo; investing 
in &amp;ldquo;enterprise&amp;rdquo;?&lt;/p>
+&lt;p>An &lt;code>EdgeLabel&lt;/code> does not support connecting multiple 
pairs of &lt;code>VertexLabels&lt;/code>, users need to split the 
&lt;code>EdgeLabel&lt;/code> into finer details, such as: &amp;ldquo;personal 
investment&amp;rdquo;, &amp;ldquo;enterprise investment&amp;rdquo;.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>通过&lt;code>RestAPI&lt;/code>发送请求时提示&lt;code>HTTP 415 Unsupported Media 
Type&lt;/code>&lt;/p>
-&lt;p>请求头中需要指定&lt;code>Content-Type:application/json&lt;/code>&lt;/p>
+&lt;p>Prompt &lt;code>HTTP 415 Unsupported Media Type&lt;/code> when sending a 
request through &lt;code>RestAPI&lt;/code>&lt;/p>
+&lt;p>&lt;code>Content-Type: application/json&lt;/code> needs to be specified 
in the request header&lt;/p>
 &lt;/li>
 &lt;/ul>
-&lt;p>其他问题可以在对应项目的 issue 区搜索,例如 &lt;a 
href="https://github.com/hugegraph/hugegraph/issues";>Server-Issues&lt;/a> / 
&lt;a href="https://github.com/hugegraph/hugegraph-loader/issues";>Loader 
Issues&lt;/a>&lt;/p></description></item></channel></rss>
\ No newline at end of file
+&lt;p>Other issues can be searched in the issue area of the corresponding 
project, such as &lt;a 
href="https://github.com/apache/hugegraph/issues";>Server-Issues&lt;/a> / &lt;a 
href="https://github.com/apache/hugegraph-loader/issues";>Loader 
Issues&lt;/a>&lt;/p></description></item></channel></rss>
\ No newline at end of file
diff --git a/docs/index.xml b/docs/index.xml
index 4d710a95..c7209cd6 100644
--- a/docs/index.xml
+++ b/docs/index.xml
@@ -9879,52 +9879,52 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 &lt;/table></description></item><item><title>Docs: 
FAQ</title><link>/docs/guides/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 
+0000</pubDate><guid>/docs/guides/faq/</guid><description>
 &lt;ul>
 &lt;li>
-&lt;p>如何选择后端存储? 选 RocksDB 还是 Cassandra 还是 Hbase 还是 Mysql?&lt;/p>
-&lt;p>根据你的具体需要来判断, 一般单机或数据量 &amp;lt; 100 亿推荐 RocksDB, 其他推荐使用分布式存储的后端集群&lt;/p>
+&lt;p>How to choose the back-end storage? Choose RocksDB or Cassandra or Hbase 
or Mysql?&lt;/p>
+&lt;p>Judge according to your specific needs. Generally, if the stand-alone 
machine or the data volume is &amp;lt; 10 billion, RocksDB is recommended, and 
other back-end clusters that use distributed storage are recommended.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>启动服务时提示:&lt;code>xxx (core dumped) xxx&lt;/code>&lt;/p>
-&lt;p>请检查 JDK 版本是否为 Java 11, 至少要求是 Java 8&lt;/p>
+&lt;p>Prompt when starting the service: &lt;code>xxx (core dumped) 
xxx&lt;/code>&lt;/p>
+&lt;p>Please check if the JDK version is Java 11, at least Java 8 is 
required&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>启动服务成功了,但是操作图时有类似于&amp;quot;无法连接到后端或连接未打开&amp;quot;的提示&lt;/p>
-&lt;p>第一次启动服务前,需要先使用&lt;code>init-store&lt;/code>初始化后端,后续版本会将提示得更清晰直接。&lt;/p>
+&lt;p>The service is started successfully, but there is a prompt similar to 
&amp;ldquo;Unable to connect to the backend or the connection is not 
open&amp;rdquo; when operating the graph&lt;/p>
+&lt;p>init-storeBefore starting the service for the first time, you need to 
use the initialization backend first , and subsequent versions will prompt more 
clearly and directly.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>所有的后端在使用前都需要执行&lt;code>init-store&lt;/code>吗,序列化的选择可以随意填写么?&lt;/p>
-&lt;p>除了&lt;code>memory&lt;/code>不需要,其他后端均需要,如:&lt;code>cassandra&lt;/code>、&lt;code>hbase&lt;/code>和&lt;code>rocksdb&lt;/code>等,序列化需一一对应不可随意填写。&lt;/p>
+&lt;p>Do all backends need to be executed before use init-store, and can the 
serialization options be filled in at will?&lt;/p>
+&lt;p>Except memorynot required, other backends are required, such as: 
&lt;code>cassandra&lt;/code>, &lt;code>hbaseand&lt;/code>, 
&lt;code>rocksdb&lt;/code>, etc. Serialization needs to be one-to-one 
correspondence and cannot be filled in at will.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>执行&lt;code>init-store&lt;/code>报错:&lt;code>Exception in thread 
&amp;quot;main&amp;quot; java.lang.UnsatisfiedLinkError: 
/tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version 
`GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)&lt;/code>&lt;/p>
-&lt;p>RocksDB需要 gcc 4.3.0 (GLIBCXX_3.4.10) 及以上版本&lt;/p>
+&lt;p>Execution &lt;code>init-store&lt;/code> error: &lt;code>Exception in 
thread &amp;quot;main&amp;quot; java.lang.UnsatisfiedLinkError: 
/tmp/librocksdbjni3226083071221514754.so: /usr/lib64/libstdc++.so.6: version 
`GLIBCXX_3.4.10' not found (required by 
/tmp/librocksdbjni3226083071221514754.so)&lt;/code>&lt;/p>
+&lt;p>RocksDB requires gcc 4.3.0 (GLIBCXX_3.4.10) and above&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>执行&lt;code>init-store.sh&lt;/code>时报错:&lt;code>NoHostAvailableException&lt;/code>&lt;/p>
-&lt;p>&lt;code>NoHostAvailableException&lt;/code> 
是指无法连接到&lt;code>Cassandra&lt;/code>服务,如果确定是要使用&lt;code>cassandra&lt;/code>后端,请先安装并启动这个服务。至于这个提示本身可能不够直白,我们会更新到文档进行说明的。&lt;/p>
+&lt;p>The error &lt;code>NoHostAvailableException&lt;/code> occurred while 
executing &lt;code>init-store.sh&lt;/code>.&lt;/p>
+&lt;p>&lt;code>NoHostAvailableException&lt;/code> means that the 
&lt;code>Cassandra&lt;/code> service cannot be connected to. If you are sure 
that you want to use the Cassandra backend, please install and start this 
service first. As for the message itself, it may not be clear enough, and we 
will update the documentation to provide further explanation.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>&lt;code>bin&lt;/code>目录下包含&lt;code>start-hugegraph.sh&lt;/code>、&lt;code>start-restserver.sh&lt;/code>和&lt;code>start-gremlinserver.sh&lt;/code>三个似乎与启动有关的脚本,到底该使用哪个&lt;/p>
-&lt;p>自0.3.3版本以来,已经把 GremlinServer 和 RestServer 合并为 HugeGraphServer 
了,使用&lt;code>start-hugegraph.sh&lt;/code>启动即可,后两个在后续版本会被删掉。&lt;/p>
+&lt;p>The &lt;code>bin&lt;/code> directory contains 
&lt;code>start-hugegraph.sh&lt;/code>, &lt;code>start-restserver.sh&lt;/code> 
and &lt;code>start-gremlinserver.sh&lt;/code>. These scripts seem to be related 
to startup. Which one should be used?&lt;/p>
+&lt;p>Since version 0.3.3, GremlinServer and RestServer have been merged into 
HugeGraphServer. To start, use start-hugegraph.sh. The latter two will be 
removed in future versions.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>配置了两个图,名字是&lt;code>hugegraph&lt;/code>和&lt;code>hugegraph1&lt;/code>,而启动服务的命令是&lt;code>start-hugegraph.sh&lt;/code>,是只打开了&lt;code>hugegraph&lt;/code>这个图吗&lt;/p>
-&lt;p>&lt;code>start-hugegraph.sh&lt;/code>会打开所有&lt;code>gremlin-server.yaml&lt;/code>的&lt;code>graphs&lt;/code>下的图,这二者并无名字上的直接关系&lt;/p>
+&lt;p>Two graphs are configured, the names are &lt;code>hugegraph&lt;/code> 
and &lt;code>hugegraph1&lt;/code>, and the command to start the service is 
&lt;code>start-hugegraph.sh&lt;/code>. Is only the hugegraph graph 
opened?&lt;/p>
+&lt;p>&lt;code>start-hugegraph.sh&lt;/code> will open all graphs under the 
graphs of &lt;code>gremlin-server.yaml&lt;/code>. The two have no direct 
relationship in name&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>服务启动成功后,使用&lt;code>curl&lt;/code>查询所有顶点时返回乱码&lt;/p>
-&lt;p>服务端返回的批量顶点/边是压缩(gzip)过的,可以使用管道重定向至 &lt;code>gunzip&lt;/code> 
进行解压(&lt;code>curl http://example | 
gunzip&lt;/code>),也可以用&lt;code>Firefox&lt;/code>的&lt;code>postman&lt;/code>或者&lt;code>Chrome&lt;/code>浏览器的&lt;code>restlet&lt;/code>插件发请求,会自动解压缩响应数据。&lt;/p>
+&lt;p>After the service starts successfully, garbled characters are returned 
when using &lt;code>curl&lt;/code> to query all vertices&lt;/p>
+&lt;p>The batch vertices/edges returned by the server are compressed (gzip), 
and can be redirected to &lt;code>gunzip&lt;/code> for decompression 
(&lt;code>curl http://example | gunzip&lt;/code>), or can be sent with the 
&lt;code>postman&lt;/code> of &lt;code>Firefox&lt;/code> or the 
&lt;code>restlet&lt;/code> plug-in of Chrome browser. request, the response 
data will be decompressed automatically.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>使用顶点Id通过&lt;code>RESTful API&lt;/code>查询顶点时返回空,但是顶点确实是存在的&lt;/p>
-&lt;p>检查顶点Id的类型,如果是字符串类型,&lt;code>API&lt;/code>的&lt;code>url&lt;/code>中的id部分需要加上双引号,数字类型则不用加。&lt;/p>
+&lt;p>When using the vertex Id to query the vertex through the 
&lt;code>RESTful API&lt;/code>, it returns empty, but the vertex does 
exist&lt;/p>
+&lt;p>Check the type of the vertex ID. If it is a string type, the 
&amp;ldquo;id&amp;rdquo; part of the API URL needs to be enclosed in double 
quotes, while for numeric types, it is not necessary to enclose the ID in 
quotes.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>已经根据需要给顶点Id加上了双引号,但是通过&lt;code>RESTful API&lt;/code>查询顶点时仍然返回空&lt;/p>
-&lt;p>检查顶点id中是否包含&lt;code>+&lt;/code>、&lt;code>空格&lt;/code>、&lt;code>/&lt;/code>、&lt;code>?&lt;/code>、&lt;code>%&lt;/code>、&lt;code>&amp;amp;&lt;/code>和&lt;code>=&lt;/code>这些URL的保留字符,如果存在则需要进行编码。下表给出了编码值:&lt;/p>
-&lt;div class="highlight">&lt;pre tabindex="0" 
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code
 class="language-fallback" data-lang="fallback">&lt;span 
style="display:flex;">&lt;span>特殊字符 | 编码值
-&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>--------| ----
+&lt;p>Vertex Id has been double quoted as required, but querying the vertex 
via the RESTful API still returns empty&lt;/p>
+&lt;p>Check whether the vertex id contains &lt;code>+&lt;/code>, 
&lt;code>space&lt;/code>, &lt;code>/&lt;/code>, &lt;code>?&lt;/code>, 
&lt;code>%&lt;/code>, &lt;code>&amp;amp;&lt;/code>, and &lt;code>=&lt;/code> 
reserved characters of these &lt;code>URLs&lt;/code>. If they exist, they need 
to be encoded. The following table gives the coded values:&lt;/p>
+&lt;div class="highlight">&lt;pre tabindex="0" 
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code
 class="language-fallback" data-lang="fallback">&lt;span 
style="display:flex;">&lt;span>special character | encoded value
+&lt;/span>&lt;/span>&lt;span 
style="display:flex;">&lt;span>------------------| -------------
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>+ | %2B
-&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>空格 | %20
+&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>space | %20
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>/ | %2F
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>? | %3F
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>% | %25
@@ -9933,43 +9933,43 @@ Merging mode as needed, and when the Restore is 
completed, restore the graph mod
 &lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>= | %3D
 &lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
 &lt;li>
-&lt;p>查询某一类别的顶点或边(&lt;code>query by label&lt;/code>)时提示超时&lt;/p>
-&lt;p>由于属于某一label的数据量可能比较多,请加上limit限制。&lt;/p>
+&lt;p>Timeout when querying vertices or edges of a certain category 
(&lt;code>query by label&lt;/code>)&lt;/p>
+&lt;p>Since the amount of data belonging to a certain label may be relatively 
large, please add a limit limit.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>通过&lt;code>RESTful 
API&lt;/code>操作图是可以的,但是发送&lt;code>Gremlin&lt;/code>语句就报错:&lt;code>Request 
Failed(500)&lt;/code>&lt;/p>
-&lt;p>可能是&lt;code>GremlinServer&lt;/code>的配置有误,检查&lt;code>gremlin-server.yaml&lt;/code>的&lt;code>host&lt;/code>、&lt;code>port&lt;/code>是否与&lt;code>rest-server.properties&lt;/code>的&lt;code>gremlinserver.url&lt;/code>匹配,如不匹配则修改,然后重启服务。&lt;/p>
+&lt;p>It is possible to operate the graph through the &lt;code>RESTful 
API&lt;/code>, but when sending &lt;code>Gremlin&lt;/code> statements, an error 
is reported: &lt;code>Request Failed(500)&lt;/code>&lt;/p>
+&lt;p>It may be that the configuration of &lt;code>GremlinServer&lt;/code> is 
wrong, check whether the &lt;code>host&lt;/code> and &lt;code>port&lt;/code> of 
&lt;code>gremlin-server.yaml&lt;/code> match the 
&lt;code>gremlinserver.url&lt;/code> of 
&lt;code>rest-server.properties&lt;/code>, if they do not match, modify them, 
and then Restart the service.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>使用&lt;code>Loader&lt;/code>导数据出现&lt;code>Socket 
Timeout&lt;/code>异常,然后导致&lt;code>Loader&lt;/code>中断&lt;/p>
-&lt;p>持续地导入数据会使&lt;code>Server&lt;/code>的压力过大,然后导致有些请求超时。可以通过调整&lt;code>Loader&lt;/code>的参数来适当缓解&lt;code>Server&lt;/code>压力(如:重试次数,重试间隔,错误容忍数等),降低该问题出现频率。&lt;/p>
+&lt;p>When using &lt;code>Loader&lt;/code> to import data, a &lt;code>Socket 
Timeout&lt;/code> exception occurs, and then &lt;code>Loader&lt;/code> is 
interrupted&lt;/p>
+&lt;p>Continuously importing data will put too much pressure on the 
&lt;code>Server&lt;/code>, which will cause some requests to time out. The 
pressure on &lt;code>Server&lt;/code> can be appropriately relieved by 
adjusting the parameters of &lt;code>Loader&lt;/code> (such as: number of 
retries, retry interval, error tolerance, etc.), and reduce the frequency of 
this problem.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>如何删除全部的顶点和边,RESTful 
API中没有这样的接口,调用&lt;code>gremlin&lt;/code>的&lt;code>g.V().drop()&lt;/code>会报错&lt;code>Vertices
 in transaction have reached capacity xxx&lt;/code>&lt;/p>
-&lt;p>目前确实没有好办法删除全部的数据,用户如果是自己部署的&lt;code>Server&lt;/code>和后端,可以直接清空数据库,重启&lt;code>Server&lt;/code>。可以使用paging
 API或scan API先获取所有数据,再逐条删除。&lt;/p>
+&lt;p>How to delete all vertices and edges. There is no such interface in the 
RESTful API. Calling &lt;code>g.V().drop()&lt;/code> of 
&lt;code>gremlin&lt;/code> will report an error &lt;code>Vertices in 
transaction have reached capacity xxx&lt;/code>&lt;/p>
+&lt;p>At present, there is really no good way to delete all the data. If the 
user deploys the &lt;code>Server&lt;/code> and the backend by himself, he can 
directly clear the database and restart the &lt;code>Server&lt;/code>. You can 
use the paging API or scan API to get all the data first, and then delete them 
one by one.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>清空了数据库,并且执行了&lt;code>init-store&lt;/code>,但是添加&lt;code>schema&lt;/code>时提示&amp;quot;xxx
 has existed&amp;quot;&lt;/p>
-&lt;p>&lt;code>HugeGraphServer&lt;/code>内是有缓存的,清空数据库的同时是需要重启&lt;code>Server&lt;/code>的,否则残留的缓存会产生不一致。&lt;/p>
+&lt;p>The database has been cleared and &lt;code>init-store&lt;/code> has been 
executed, but when trying to add a schema, the prompt &amp;ldquo;xxx has 
existed&amp;rdquo; appeared.&lt;/p>
+&lt;p>There is a cache in the &lt;code>HugeGraphServer&lt;/code>, and it is 
necessary to restart the &lt;code>Server&lt;/code> when the database is 
cleared, otherwise the residual cache will be inconsistent.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>插入顶点或边的过程中报错:&lt;code>Id max length is 128, but got xxx {yyy}&lt;/code> 
或 &lt;code>Big id max length is 32768, but got xxx&lt;/code>&lt;/p>
-&lt;p>为了保证查询性能,目前的后端存储对id列的长度做了限制,顶点id不能超过128字节,边id长度不能超过32768字节,索引id不能超过128字节。&lt;/p>
+&lt;p>An error is reported during the process of inserting vertices or edges: 
&lt;code>Id max length is 128, but got xxx {yyy}&lt;/code> or &lt;code>Big id 
max length is 32768, but got xxx&lt;/code>&lt;/p>
+&lt;p>In order to ensure query performance, the current backend storage limits 
the length of the id column. The vertex id cannot exceed 128 bytes, the edge id 
cannot exceed 32768 bytes, and the index id cannot exceed 128 bytes.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>是否支持嵌套属性,如果不支持,是否有什么替代方案&lt;/p>
-&lt;p>嵌套属性目前暂不支持。替代方案:可以把嵌套属性作为单独的顶点拿出来,然后用边连接起来。&lt;/p>
+&lt;p>Is there support for nested attributes, and if not, are there any 
alternatives?&lt;/p>
+&lt;p>Nested attributes are currently not supported. Alternative: Nested 
attributes can be taken out as individual vertices and connected with 
edges.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>一个&lt;code>EdgeLabel&lt;/code>是否可以连接多对&lt;code>VertexLabel&lt;/code>,比如&amp;quot;投资&amp;quot;关系,可以是&amp;quot;个人&amp;quot;投资&amp;quot;企业&amp;quot;,也可以是&amp;quot;企业&amp;quot;投资&amp;quot;企业&amp;quot;&lt;/p>
-&lt;p>一个&lt;code>EdgeLabel&lt;/code>不支持连接多对&lt;code>VertexLabel&lt;/code>,需要用户将&lt;code>EdgeLabel&lt;/code>拆分得更细一点,如:&amp;ldquo;个人投资&amp;rdquo;,&amp;ldquo;企业投资&amp;rdquo;。&lt;/p>
+&lt;p>Can an &lt;code>EdgeLabel&lt;/code> connect multiple pairs of 
&lt;code>VertexLabel&lt;/code>, such as &amp;ldquo;investment&amp;rdquo; 
relationship, which can be &amp;ldquo;individual&amp;rdquo; investing in 
&amp;ldquo;enterprise&amp;rdquo;, or &amp;ldquo;enterprise&amp;rdquo; investing 
in &amp;ldquo;enterprise&amp;rdquo;?&lt;/p>
+&lt;p>An &lt;code>EdgeLabel&lt;/code> does not support connecting multiple 
pairs of &lt;code>VertexLabels&lt;/code>, users need to split the 
&lt;code>EdgeLabel&lt;/code> into finer details, such as: &amp;ldquo;personal 
investment&amp;rdquo;, &amp;ldquo;enterprise investment&amp;rdquo;.&lt;/p>
 &lt;/li>
 &lt;li>
-&lt;p>通过&lt;code>RestAPI&lt;/code>发送请求时提示&lt;code>HTTP 415 Unsupported Media 
Type&lt;/code>&lt;/p>
-&lt;p>请求头中需要指定&lt;code>Content-Type:application/json&lt;/code>&lt;/p>
+&lt;p>Prompt &lt;code>HTTP 415 Unsupported Media Type&lt;/code> when sending a 
request through &lt;code>RestAPI&lt;/code>&lt;/p>
+&lt;p>&lt;code>Content-Type: application/json&lt;/code> needs to be specified 
in the request header&lt;/p>
 &lt;/li>
 &lt;/ul>
-&lt;p>其他问题可以在对应项目的 issue 区搜索,例如 &lt;a 
href="https://github.com/hugegraph/hugegraph/issues";>Server-Issues&lt;/a> / 
&lt;a href="https://github.com/hugegraph/hugegraph-loader/issues";>Loader 
Issues&lt;/a>&lt;/p></description></item><item><title>Docs: IndexLabel 
API</title><link>/docs/clients/restful-api/indexlabel/</link><pubDate>Mon, 01 
Jan 0001 00:00:00 
+0000</pubDate><guid>/docs/clients/restful-api/indexlabel/</guid><description>
+&lt;p>Other issues can be searched in the issue area of the corresponding 
project, such as &lt;a 
href="https://github.com/apache/hugegraph/issues";>Server-Issues&lt;/a> / &lt;a 
href="https://github.com/apache/hugegraph-loader/issues";>Loader 
Issues&lt;/a>&lt;/p></description></item><item><title>Docs: IndexLabel 
API</title><link>/docs/clients/restful-api/indexlabel/</link><pubDate>Mon, 01 
Jan 0001 00:00:00 
+0000</pubDate><guid>/docs/clients/restful-api/indexlabel/</guid><description>
 &lt;h3 id="15-indexlabel">1.5 IndexLabel&lt;/h3>
 &lt;p>假设已经创建好了1.1.3中的 PropertyKeys 、1.2.3中的 VertexLabels 以及 1.3.3中的 
EdgeLabels&lt;/p>
 &lt;h4 id="151-创建一个indexlabel">1.5.1 创建一个IndexLabel&lt;/h4>
diff --git a/en/index.html b/en/index.html
index 017c4d50..2b641798 100644
--- a/en/index.html
+++ b/en/index.html
@@ -1 +1 @@
-<!doctype html><html lang=cn><head><title>/</title><link rel=canonical 
href=/><meta name=robots content="noindex"><meta charset=utf-8><meta 
http-equiv=refresh content="0; url=/"></head></html>
\ No newline at end of file
+<!doctype html><html lang=en><head><title>/</title><link rel=canonical 
href=/><meta name=robots content="noindex"><meta charset=utf-8><meta 
http-equiv=refresh content="0; url=/"></head></html>
\ No newline at end of file
diff --git a/en/sitemap.xml b/en/sitemap.xml
index a1bc257f..793240b5 100644
--- a/en/sitemap.xml
+++ b/en/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset 
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"; 
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/guides/architectural/</loc><lastmod>2023-05-12T23:46:05-05:00</lastmod><xhtml:link
 rel="alternate" hreflang="cn" 
href="/cn/docs/guides/architectural/"/><xhtml:link rel="alternate" 
hreflang="en" 
href="/docs/guides/architectural/"/></url><url><loc>/docs/config/config-guide/</loc><lastmod>2023-05-10T12:08:15+08:00</last
 [...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset 
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"; 
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/guides/architectural/</loc><lastmod>2023-05-12T23:46:05-05:00</lastmod><xhtml:link
 rel="alternate" hreflang="cn" 
href="/cn/docs/guides/architectural/"/><xhtml:link rel="alternate" 
hreflang="en" 
href="/docs/guides/architectural/"/></url><url><loc>/docs/config/config-guide/</loc><lastmod>2023-05-10T12:08:15+08:00</last
 [...]
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index ed1e10a3..c71a2cb4 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><sitemapindex 
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";><sitemap><loc>/cn/sitemap.xml</loc><lastmod>2023-05-14T19:35:13+08:00</lastmod></sitemap><sitemap><loc>/en/sitemap.xml</loc><lastmod>2023-05-14T07:26:12-05:00</lastmod></sitemap></sitemapindex>
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><sitemapindex 
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";><sitemap><loc>/en/sitemap.xml</loc><lastmod>2023-05-14T07:28:41-05:00</lastmod></sitemap><sitemap><loc>/cn/sitemap.xml</loc><lastmod>2023-05-14T19:35:13+08:00</lastmod></sitemap></sitemapindex>
\ No newline at end of file

Reply via email to