Merge 3.3 to master (#1812)

* Merge to v3.3.0 * Update deploy.yml * Update deploy.yml * Update 0.FAQ.md (#1738) * Update deploy.yml * Update deploy.yml * Update deploy.yml * Fix favicon * fix: missing file causing doc search issue (#1740) * Update 2.deploy-dashboard.md * Update 4.use-dashboard.md * Update ex-ug-deploy.md * Update nebula-analytics.md * Update ex-ug-connect.md * Update nebula-analytics.md * Update nebula-algorithm.md * Update nebula-algorithm.md * Update ex-ug-what-is-explorer.md * Update ex-ug-what-is-exchange.md * Update explorer-release-note.md * Update 2.deploy-connect-dashboard-ent.md * Update st-ug-limitations.md * add-note-for-multiple-data-storage-directories- (#1741) * Update 0.FAQ.md * Update mkdocs.yml (#1747) * Update 6.eco-tool-version.md (#1748) * update dashboard and explorer (#1749) * Update ex-ug-what-is-exchange.md (#1750) * Update 1.prepare-resources.md (#1751) * add-length()-and-size() (#1752) * explorer removes dependence on studio (#1753) * update workflow (#1754) * Update ex-ug-deploy.md * Update ex-ug-deploy.md * dashboard update create cluster (#1756) * Update 2.balance-syntax.md (#1758) * Move std() sum() to aggregating functions and add collect examples (#1759) * move-std()-sum()-to-aggregating-functions-and-add-collect-examples * Update 15.aggregating.md * Update error-code.md (#1760) * add hdfs error for dag (#1761) * update ngql template (#1763) * Update optional-match.md (#1764) * merge helm in studio doc (#1765) * br-release-3.3.0 (#1767) * typo fix in insert edge page (#1762) * remove docker from local deployment (#1768) * fix links (#1769) * Fix links 2 (#1770) * fix links * update * Implicit group by (#1771) * implicit-group-by * Update group-by.md * Update group-by.md * update TIMESTAMP (#1772) * add-example-for-getting-vertex/edge-without-specifying-tag/edge-type (#1773) * add-example-for-getting-vertex/edge-without-specifying-tag/edge-type * Update 2.match.md * Update 2.deploy-connect-dashboard-ent.md * Dashboard update 3.2.2 (#1775) * add-note-for-supporting-arm (#1776) * why-space-0-not-found (#1777) * why-space-0-not-found (#1778) * br-opts-330 (#1782) * add-release-notes-on-the-default-page (#1783) * Update 4.schema.md (#1784) * Add release notes on the default page (#1787) * add-release-notes-on-the-default-page * Update README.md * Update README.md * Update 3.go.md (#1790) * about-linux-operating-system (#1789) * wording-revision-of-schema-related-functions (#1793) * dashboard release 3.2.3 (#1794) * Update ex-ug-deploy.md * timestamp()-supports-int (#1795) * Update 1.resource-preparations.md (#1797) * Update 5.lookup.md (#1798) * Update 10.create-schema.md * Update config-without-header.md * exchange update faq (#1800) * Update 2.compile-br.md (#1801) * dashboard release 3.2.4 (#1802) * explorer release 3.2.1 (#1803) * Let it snow (#1805) * Revert "Let it snow (#1805)" (#1806) This reverts commit a14d2ef. * Update nebula-analytics.md * Update 1.get-subgraph.md (#1807) * Update 4.schema.md (#1809) * Update 3.connect-dashboard.md * Update 3.go.md (#1808) * update ga code for 3.3.0 (#1774) * Update 0.FAQ.md * Unified dashboard directory structure (#1810) * Update 2.match.md (#1811) * update * Update extra.css * Update use-importer.md * Update mkdocs.yml Co-authored-by: abby.huang <78209557+abby-cyber@users.noreply.github.com> Co-authored-by: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Co-authored-by: randomJoe211 <69501902+randomJoe211@users.noreply.github.com> Co-authored-by: Jerry Liang <8124783+nianiaJR@users.noreply.github.com> Co-authored-by: Wey Gu <weyl.gu@gmail.com>
vesoft-inc · Dec 21, 2022 · 96f7f9f · 96f7f9f
1 parent ceaa41c
commit 96f7f9f
Show file tree

Hide file tree

Showing 71 changed files with 1,016 additions and 649 deletions.
diff --git a/docs-2.0/2.quick-start/4.nebula-graph-crud.md b/docs-2.0/2.quick-start/4.nebula-graph-crud.md
@@ -85,6 +85,10 @@ In this topic, we will use the following dataset to demonstrate basic CRUD opera
     nebula> CREATE SPACE basketballplayer(partition_num=15, replica_factor=1, vid_type=fixed_string(30));
     ```
 
+  !!! note
+
+        If the system returns the error `[ERROR (-1005)]: Host not enough!`, check whether [registered the Storage Service](../2.quick-start/3.1add-storage-hosts.md).
+
 2. Check the partition distribution with `SHOW HOSTS` to make sure that the partitions are distributed in a balanced way.
 
     ```ngql

diff --git a/docs-2.0/2.quick-start/6.cheatsheet-for-ngql.md b/docs-2.0/2.quick-start/6.cheatsheet-for-ngql.md
@@ -31,7 +31,7 @@
   | bit_and()                               | Bitwise AND.                                                 |
   | bit_or()                                | Bitwise OR.                                                  |
   | bit_xor()                               | Bitwise XOR.                                                 |
-  | int size()                              | Returns the number of elements in a list or a map.           |
+  | int size()                              | Returns the number of elements in a list or a map or the length of a string.           |
   | int range(int start, int end, int step) | Returns a list of integers from `[start,end]` in the specified steps. `step` is 1 by default. |
   | int sign(double x)                      | Returns the signum of the given number.<br/>If the number is `0`, the system returns `0`.<br/>If the number is negative, the system returns `-1`.<br/>If the number is positive, the system returns `1`. |
   | double e()                              | Returns the base of the natural logarithm, e (2.718281828459045). |
@@ -60,7 +60,7 @@
   |string toLower(string a) | The same as `lower()`. |
   |string upper(string a) | Returns the argument in uppercase. |
   |string toUpper(string a) | The same as `upper()`. |
-  |int length(string a) | Returns the length of the given string in bytes. |
+  |int length(a) | Returns the length of the given string in bytes or the length of a path in hops. |
   |string trim(string a) | Removes leading and trailing spaces. |
   |string ltrim(string a) | Removes leading spaces. |
   |string rtrim(string a) | Removes trailing spaces. |
@@ -82,13 +82,13 @@
 
   |Function| Description |
   |----  |  ----|
-  |int now()  | Returns the current date and time of the system timezone. |
-  |timestamp timestamp() | Returns the current date and time of the system timezone. |
+  |int now()  | Returns the current timestamp of the system. |
+  |timestamp timestamp() | Returns the current timestamp of the system. |
   |date date() | Returns the current UTC date based on the current system. |
   |time time() | Returns the current UTC time based on the current system. |
   |datetime datetime() | Returns the current UTC date and time based on the current system. |  
 
-* [Schema functions](../3.ngql-guide/6.functions-and-expressions/4.schema.md)
+* [Schema-related functions](../3.ngql-guide/6.functions-and-expressions/4.schema.md)
 
   * For nGQL statements
 
@@ -185,14 +185,14 @@
   | Match vertices                      | `(v)`                                                        | You can use a user-defined variable in a pair of parentheses to represent a vertex in a pattern. For example: `(v)`. |
   | Match tags                     | `MATCH (v:player) RETURN v`                                  | You can specify a tag with `:<tag_name>` after the vertex in a pattern.           |
   | Match multiple tags | `MATCH (v:player:team) RETURN v LIMIT 10` | To match vertices with multiple tags, use colons (:). |
-  | Match vertex properties                | `MATCH (v:player{name:"Tim Duncan"}) RETURN v`               | You can specify a vertex property with `{<prop_name>: <prop_value>}` after the tag in a pattern. |
+  | Match vertex properties                | `MATCH (v:player{name:"Tim Duncan"}) RETURN v`  <br><br>`MATCH (v) WITH v, properties(v) as props, keys(properties(v)) as kk LIMIT 10000 WHERE [i in kk where props[i] == "Tim Duncan"] RETURN v`             | You can specify a vertex property with `{<prop_name>: <prop_value>}` after the tag in a pattern; or use a vertex property value to get vertices directly. |
   | Match a VID.                  | `MATCH (v) WHERE id(v) == 'player101' RETURN v`              | You can use the VID to match a vertex. The `id()` function can retrieve the VID of a vertex.         |
   | Match multiple VIDs.                  | `MATCH (v:player { name: 'Tim Duncan' })--(v2) WHERE id(v2) IN ["player101", "player102"] RETURN v2` | To match multiple VIDs, use `WHERE id(v) IN [vid_list]`.        |
   | Match connected vertices                | `MATCH (v:player{name:"Tim Duncan"})--(v2) RETURN v2.player.name AS Name` | You can use the `--` symbol to represent edges of both directions and match vertices connected by these edges. You can add a `>` or `<` to the `--` symbol to specify the direction of an edge. |
   | Match paths                    | `MATCH p=(v:player{name:"Tim Duncan"})-->(v2) RETURN p`      | Connected vertices and edges form a path. You can use a user-defined variable to name a path as follows. |
   | Match edges                      | `MATCH (v:player{name:"Tim Duncan"})-[e]-(v2) RETURN e`<br>`MATCH ()<-[e]-() RETURN e LIMIT 3`      | Besides using `--`, `-->`, or `<--` to indicate a nameless edge, you can use a user-defined variable in a pair of square brackets to represent a named edge. For example: `-[e]-`. |
   | Match an edge type              | `MATCH ()-[e:follow]-() RETURN e LIMIT 5`                            |Just like vertices, you can specify an edge type with `:<edge_type>` in a pattern. For example: `-[e:follow]-`. |
-  | Match edge type properties                | ` MATCH (v:player{name:"Tim Duncan"})-[e:follow{degree:95}]->(v2) RETURN e` | You can specify edge type properties with `{<prop_name>: <prop_value>}` in a pattern. For example: `[e:follow{likeness:95}]`. |
+  | Match edge type properties                | ` MATCH (v:player{name:"Tim Duncan"})-[e:follow{degree:95}]->(v2) RETURN e` <br><br>`MATCH ()-[e]->() WITH e, properties(e) as props, keys(properties(e)) as kk LIMIT 10000 WHERE [i in kk where props[i] == 90] RETURN e`| You can specify edge type properties with `{<prop_name>: <prop_value>}` in a pattern. For example: `[e:follow{likeness:95}]`; or use an edge type property value to get edges directly. |
   | Match multiple edge types           | `MATCH (v:player{name:"Tim Duncan"})-[e:follow | :serve]->(v2) RETURN e` | The `|` symbol can help matching multiple edge types. For example: `[e:follow|:serve]`. The English colon (:) before the first edge type cannot be omitted, but the English colon before the subsequent edge type can be omitted, such as `[e:follow|serve]`. |
   | Match multiple edges                  | `MATCH (v:player{name:"Tim Duncan"})-[]->(v2)<-[e:serve]-(v3) RETURN v2, v3` | You can extend a pattern to match multiple edges in a path.                       |
   | Match fixed-length paths               | `MATCH p=(v:player{name:"Tim Duncan"})-[e:follow*2]->(v2) RETURN DISTINCT v2 AS Friends` | You can use the `:<edge_type>*<hop>` pattern to match a fixed-length path. `hop` must be a non-negative integer. The data type of `e` is the list.|

diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md
@@ -293,7 +293,7 @@ Or get vertices by each tag, and then group them by yourself.
 
 Yes, for more information, see [Keywords and reserved words](../3.ngql-guide/1.nGQL-overview/keywords-and-reserved-words.md).
 
-### "How to get the out-degree/the in-degree of a vertex with a given name?"
+### "How to get the out-degree/the in-degree of a given vertex?"
 
 The out-degree of a vertex refers to the number of edges starting from that vertex, while the in-degree refers to the number of edges pointing to that vertex.
 
@@ -388,9 +388,9 @@ If you have not modified the predefined ports in the [Configurations](../5.confi
 
 | Service | Port                      |
 |---------|---------------------------|
-| Meta    | 9559, 9560, 19559, 19560  |
-| Graph   | 9669, 19669, 19670        |
-| Storage | 9777 ~ 9780, 19779, 19780 |
+| Meta    | 9559, 9560, 19559  |
+| Graph   | 9669, 19669   |
+| Storage | 9777 ~ 9780, 19779|
 
 If you have customized the configuration files and changed the predefined ports, find the port numbers in your configuration files and open them on the firewalls.
 

diff --git a/docs-2.0/20.appendix/6.eco-tool-version.md b/docs-2.0/20.appendix/6.eco-tool-version.md
@@ -146,6 +146,18 @@ Docker Compose can quickly deploy NebulaGraph clusters. For how to use it, pleas
 |:---|:---|
 | {{ nebula.tag }}  | {{br.tag}}|
 
+
+{{ent.ent_begin}}
+## Backup & Restore Enterprise Edition
+
+Backup Restore (BR for short) Enterprise Edition is a Command-Line Interface (CLI) tool. With BR Enterprise Edition, you can back up and restore NebulaGraph Enterprise Edition data.
+
+|NebulaGraph version|BR version|
+|:---|:---|
+| {{ nebula.tag }}  | {{br_ent.tag}}|
+
+{{ent.ent_end}}
+
 ## NebulaGraph Bench
 
 [NebulaGraph Bench](https://github.com/vesoft-inc/nebula-bench/releases/tag/{{bench.tag}}) is used to test the baseline performance data of NebulaGraph. It uses the standard data set of LDBC.