Merge v3.1.0 into master (#1370)

* publish 3.1.0 (#1282)

* link fix (#1283)

* Update mkdocs.yml (#1285)

* Update st-ug-release-note.md

* Update load-balance.md (#1284)

* Update load-balance.md

* Update load-balance.md

* Update load-balance.md

* Update docs-2.0/8.service-tuning/load-balance.md

Co-authored-by: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com>

* add one more note (#1286)

* Update mkdocs.yml (#1287)

* add limits for using Operator (#1288)

* pic error fix (#1289)

* Update mkdocs.yml (#1290)

* Update nebula-algorithm.md (#1291)

* error fix (#1292)

* Update 1.get-subgraph.md (#1293)

* Update 1.create-native-index.md

* change theme color to red (#1294)

* Update 2.find-path.md

* Update 1.explain-and-profile.md

* Update mkdocs.yml

* Update mkdocs.yml

* fix release

* Update source_manage-service.md

* Update 1.configurations.md

* Update 1.configurations.md

* Update 3.graph-config.md

* Update 4.storage-config.md

* fix release

* Update 2.compile-br.md

* Update mkdocs.yml (#1297)

* Update 2.deploy-connect-dashboard-ent.md (#1298)

* Update 2.deploy-connect-dashboard-ent.md

* Update 2.deploy-connect-dashboard-ent.md

* fix tag

* switch sync data (#1299)

* fix punctuation

* mike set default for 3.1.0 (#1295)

* fix gateway

* mix nebula.tag

* fix tag

* macro fix (#1300)

* macro fix (#1300)

* Update 3.manage-snapshot.md

* Update 2.1.show-create-index.md

* merge

* Update 4.delete-edge.md (#1301)

* Optimization for ngql overview (#1302)

* Update 1.overview.md

* Update 1.overview.md

* Update 1.resource-preparations.md (#1303)

* add cloud (#1304)

* Update 1.resource-preparations.md

* Update 1.install-nebula-graph-by-compiling-the-source-code.md

* Update 6.clear-space.md (#1305)

* Update 1.install-nebula-graph-by-compiling-the-source-code.md

* Update nebula-bench.md

* Update learning-path.md

* Update learning-path.md

* Update source_install-nebula-graph-by-rpm-or-deb.md

* Update 6.eco-tool-version.md

* Update ex-ug-deploy.md (#1306)

* Update deploy-nebula-graph-cluster.md

* Update standalone-deployment.md

* Update source_connect-to-nebula-graph.md

* Update manage-storage-host.md

* Update 1.configurations.md

* Update 1.configurations.md

* Update mkdocs.yml (#1307)

rename release note url path

* Update audit-log.md

* modify typo (#1308)

* Update 4.ldap.md

* Update 4.ldap.md

* Update load-balance.md

* Update mkdocs.yml (#1309)

* Update practice.md

* Update nebula-console.md

* Update use-importer.md (#1311)

* Update 10.geography.md (#1312)

* Add note for dashboard exposure (#1310)

* add note for dashboard exposure

* Update 1.resource-preparations.md

* fix pdf admonition

* add doc for better exposure of peripherals (#1313)

* Update 0-2.relates.md

* unify release-note

* Update use-importer.md

modify release linked macro name

* Update 2.deploy-dashboard.md

* Update 1.resource-preparations.md

* Update disk space requirement in upgrade doc (#1315)

Co-authored-by: randomJoe211 <69501902+randomJoe211@users.noreply.github.com>

* Update 1.resource-preparations.md

* result-changes-for-status-all-before-adding-hosts (#1319)

* systemd note available for nebula-ent created by dashboard (#1318)

* comment sed (#1316)

* Update 18.show-queries.md (#1324)

* Update 4.install-nebula-graph-from-tar.md (#1323)

* Update 17.show-sessions.md (#1322)

* Config changes for quick start (#1321)

* Update 4.show-create-space.md (#1320)

* Update 14.geo.md (#1317)

* Update 6.cheatsheet-for-ngql.md (#1325)

* Update 1.comparison.md (#1326)

* Update with.md (#1335)

* Update yield.md (#1334)

* Update where.md (#1333)

* Update limit.md (#1332)

* Update return.md (#1331)

* Update order-by.md (#1330)

* Update limit.md (#1329)

* translate the benchmark report of v3.1.0 (#1342)

* translate the benchmark report of v3.1.0

* Update translation/310-performance-report.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Create 2.plato_doc.md (#1343)

* Sub  and superscripts test (#1341)

* formatting fix test

* Update 1.math.md

* Update mkdocs.yml

* Update 2.string.md (#1340)

* Update 2.drop-edge.md (#1339)

* Update 1.create-edge.md (#1338)

* Update 2.drop-tag.md (#1337)

* Update 4.describe-space.md (#1336)

* update explorer (#1344)

* Update st-ug-release-note.md (#1347)

* Update 4.date-and-time.md

* Update st-ug-release-note.md

* Update mkdocs.yml

* Update st-ug-deploy.md

* Fix a few typos (#1346)

* Update mkdocs.yml (#1350)

* rename studio (#1351)

* Update mkdocs.yml (#1353)

* Update st-ug-release-note.md (#1348)

* Delete cluster with helm (#1355)

* Update mkdocs.yml

* Update 3.2create-cluster-with-helm.md

* Update 1.create-space.md (#1349)

* Update 3.graph-service.md (#1356)

* Update ex-ug-import-from-mysql.md (#1360)

* Update ex-ug-parameter.md (#1361)

* Update 0-1-graph-database.md (#1362)

* Update 3.nebula-cpp-client.md (#1357)

* Update 3.1create-cluster-with-kubectl.md (#1359)

* Update 3.1create-cluster-with-kubectl.md

* Update 3.1create-cluster-with-kubectl.md

Co-authored-by: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com>

* optimize explorer (#1352)

* optimize explorer

* Update docs-2.0/nebula-explorer/ex-ug-query-exploration.md

* Update docs-2.0/nebula-explorer/node-filtering.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* update docker (#1328)

* update docker

* Update docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/3.deploy-nebula-graph-with-docker-compose.md

* Update docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/3.deploy-nebula-graph-with-docker-compose.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update mkdocs.yml (#1363)

* fixes (#1364)

* Update the way to keep THP disabled (#1366)

* Update the way to keep THP disabled

* Update 6.kernel-config.md

* optimize explorer (#1365)

* optimize explorer

* Update docs-2.0/nebula-explorer/12.query-visually.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update docs-2.0/nebula-explorer/12.query-visually.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update docs-2.0/nebula-explorer/12.query-visually.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update docs-2.0/nebula-explorer/12.query-visually.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update docs-2.0/nebula-explorer/12.query-visually.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* Update docs-2.0/nebula-explorer/ex-ug-graph-exploration.md

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com>

* error code (#1367)

* Update 12.query-visually.md (#1368)

* update error code (#1369)

* configs for master

Co-authored-by: foesa <35463247+foesa-yang@users.noreply.github.com>
Co-authored-by: randomJoe211 <69501902+randomJoe211@users.noreply.github.com>
Co-authored-by: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com>
Co-authored-by: min.wu <50101159+whitewum@users.noreply.github.com>
Co-authored-by: whitewum <min.wu@vesoft.com>
Co-authored-by: Steam <evaz1879@gmail.com>
Co-authored-by: jamie.liu <57335825+jamieliu1023@users.noreply.github.com>

.github/workflows/deploy.yml

@@ -6,37 +6,27 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
         with:
-          fetch-depth: 0 # fetch all commits/branches
+          fetch-depth: 0 # fetch all commits/branches for gitversion
 
       - name: Setup Python
         uses: actions/setup-python@v1
         with:
-          python-version: '3.7'
+          python-version: '3.8'
           architecture: 'x64'
 
-      - name: apt install
-        run: |
-          sudo apt update -y
-          sudo apt install -y $(cat pkglist.txt)
-
-      - name: Install dependencies
-        run: |
-          pip3 install --upgrade pip
-          pip3 install -r ./requirements.txt
+      - name : prepare
+        run: sh ./prepare.sh 
 
       - name: Git Config
         run: git config user.name whitewum && git config user.email min.wu@vesoft.com
-
-      - name: Mike Deploy
-        run: |
-          mike list
 
       - name: Mike Deploy master
         run: |
+          # mike delete master -p
           mike deploy master -p --rebase
           mike list
 

docs-2.0/1.introduction/0-0-graph.md

@@ -2,7 +2,7 @@
 
 People from tech giants (such as Amazon and Facebook) to small research teams are devoting significant resources to exploring the potential of graph databases to solve data relationships problems. What exactly is a graph database? What can it do? Where does it fit in the database landscape? To answer these questions, we first need to understand graphs.
 
-Graphs are one of the main areas of research in computer science. Graphs can efficiently solve many of the problems that exist today. This topic will start with graphs to explain the advantages of graph databases and their great potential in modern application development, and then describe the differences between distributed graph databases and several other types of databases.
+Graphs are one of the main areas of research in computer science. Graphs can efficiently solve many of the problems that exist today. This topic will start with graphs and explain the advantages of graph databases and their great potential in modern application development, and then describe the differences between distributed graph databases and several other types of databases.
 
 ## What are graphs?
 
@@ -30,7 +30,7 @@ Simply put, graph theory is the study of graphs. Graph theory began in the early
 
 [^171]: Souce of the picture: https://medium.freecodecamp.org/i-dont-understand-graph-theory-1c96572a1401.
 
-To solve this problem, the great mathematician Euler by abstracting the four regions of the city into points and the seven bridges connecting the city into edges connecting the points, proved that the problem was unsolvable. The simplified abstract diagram is as follows [^063].
+To solve this problem, the great mathematician Euler proved that the problem was unsolvable by abstracting the four regions of the city into points and the seven bridges connecting the city into edges connecting the points. The simplified abstract diagram is as follows [^063].
 
 ![image](https://user-images.githubusercontent.com/42762957/91538126-e578b900-e949-11ea-980c-5704254e8063.png)
 
@@ -48,15 +48,13 @@ From a mathematical point of view, graph theory studies the relationships betwee
 
 In real life, there are many examples of property graphs.
 
-For example, Qichacha or BOSS Zhipin use graphs to model business equity relationships. A vertex is usually a natural person or a business, and the edge is the equity relationship between a person and a business. The properties on vertices can be the name, age, ID number, etc. of the natural person. The properties on edges can be the investment amount, investment time, position such as director and supervisor.
-
-![image](https://docs-cdn.nebula-graph.com.cn/books/images/enterprise-relations.png)
+For example, Qichacha or BOSS Zhipin use graphs to model business equity relationships. A vertex usually represents a natural person or a business, and the edge represents the equity relationship between a person and a business. The properties on vertices can be the name, age, ID number, etc. of the natural person. The properties on edges can be the investment amount, investment time, position such as director and supervisor.
 
 A vertex can be a listed company and an edge can be a correlation between listed companies. The vertex property can be a stock code, abbreviation, market capitalization, sector, etc. The edge property can be the time-series correlation coefficient of the stock price [^T01].
 
 [^T01]: https://nebula-graph.com.cn/posts/stock-interrelation-analysis-jgrapht-nebula-graph/
 
-The graph relationship can also be similar to the character relationship in a TV series like Game of Thrones [^s-01]. Vertices are the characters. Edges are the interactions between the characters. Vertex properties are the character's names, ages, camps, etc., and edge properties are the number of interactions between two characters. 
+The graph relationship can also be similar to the character relationship in a TV series like Game of Thrones [^s-01]. Vertices stand for the characters. Edges represent the interactions between the characters. Vertex properties are the character's names, ages, camps, etc., and edge properties are the number of interactions between two characters. 
 
 ![image](https://docs-cdn.nebula-graph.com.cn/books/images/game-of-thrones-01.png)
 

docs-2.0/1.introduction/0-1-graph-database.md

@@ -4,7 +4,7 @@ Now that we have discussed what a graph is, let's move on to further understandi
 
 Different graph databases may differ slightly in terms of terminology, but in the end, they all talk about vertices, edges, and properties. As for more advanced features such as labels, indexes, constraints, TTL, long tasks, stored procedures, and UDFs, these advanced features will vary significantly from one graph database to another.
 
-Graph databases use graphs to store data, and graphs are one of the closest to highly flexible, high-performance data structures. A graph database is a storage engine specifically designed to store and retrieve large information, which efficiently stores data as vertices and edges and allows high-performance retrieval and querying of these vertex-edge structures. We can also add properties to these vertices and edges.
+Graph databases use graphs to store data, and the graph structure is one of the structures that are closest to high flexibility and high performance. A graph database is a storage engine specifically designed to store and retrieve large information, which efficiently stores data as vertices and edges and allows high-performance retrieval and querying of these vertex-edge structures. We can also add properties to these vertices and edges.
 
 ## Third-party services market predictions
 
@@ -38,11 +38,11 @@ Until recently, graph databases and related graph technologies were ranked in th
 
 [^Gartner2]: https://www.gartner.com/smarterwithgartner/gartner-top-10-data-and-analytics-trends-for-2021/
 
-It can be noted that Gartner's predictions match the DB-Engines ranking well. There is usually a period of rapid bubble development, then a plateau period, followed by a new bubble period due to the emergence of new technologies, and then a plateau period. And so on in a spiral.
+It can be noted that Gartner's predictions match the DB-Engines ranking well. There is usually a period of rapid bubble development, then a plateau period, followed by a new bubble period due to the emergence of new technologies, and then a plateau period again. 
 
 ### Market size of graph databases
 
-According to statistics and forecasts from Verifiedmarketresearc[^ver], fnfresearch[^fnf], MarketsandMarkets[^mam], and Gartner[^gar], the global graph database market size to grow from about USD 0.8 billion in 2019 to USD 3-4 billion by 2026, at a Compound Annual Growth Rate (CAGR) of about 25%, which corresponds to about 5%-10% market share of the global database market. 
+According to statistics and forecasts from Verifiedmarketresearc[^ver], fnfresearch[^fnf], MarketsandMarkets[^mam], and Gartner[^gar], the global graph database market size is about to grow from about USD 0.8 billion in 2019 to USD 3-4 billion by 2026, at a Compound Annual Growth Rate (CAGR) of about 25%, which corresponds to about 5%-10% market share of the global database market. 
 
 ![Image](https://www.verifiedmarketresearch.com/wp-content/uploads/2020/10/Graph-Database-Market-Size.jpg)
 
@@ -104,6 +104,7 @@ Although this network model greatly improved productivity, its performance has b
 In the first public release of Neo4j ( Neo4j 1.4，2011), the data model was consisted of vertices and typed edges. Vertices and edges have properties. The early versions of Neo4j did not have indexes. Applications had to construct their search structure from the root vertex. Because this was very unwieldy for the applications, Neo4j 2.0 (2013.12) introduced a new concept label on vertices. Based on labels, Neo4j can index some predefined vertex properties.
 
 "Vertex", "Relationship", "Property", "Relationships can only have one label.", "Vertices can have zero or multiple labels.". All these concepts form the data model definitions for Neo4j property graphs. With the later addition of indexing, Cypher became the main way of interacting with Neo4j. This is because the application developer only needs to focus on the data itself, not on the search structure that the developer built himself as mentioned above.
+
 #### The creation of Gremlin 
 
 Gremlin is a graph query language based on Apache TinkerPop, which is close in style to a sequence of function (procedure) calls. Initially, Neo4j was queried through the Java API. applications could embed the query engine as a library into the application and then use the API to query the graph.