From 3f7c472e5a2811c9d9864132131dd3faffb2d2f8 Mon Sep 17 00:00:00 2001 From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Date: Tue, 29 Nov 2022 09:44:35 +0800 Subject: [PATCH 1/3] release 3.1.3-ent --- .github/workflows/deploy.yml | 10 +- .../4.storage-service.md | 2 +- docs-2.0/20.appendix/0.FAQ.md | 4 +- docs-2.0/20.appendix/6.eco-tool-version.md | 4 +- docs-2.0/20.appendix/learning-path.md | 2 +- .../10.tag-statements/2.drop-tag.md | 6 +- .../12.vertex-statements/1.insert-vertex.md | 13 +- .../6.functions-and-expressions/4.schema.md | 4 +- ...d => upgrade-nebula-from-300-to-latest.md} | 11 +- .../upgrade-nebula-graph-to-latest.md | 37 +- docs-2.0/8.service-tuning/3.system-design.md | 2 +- docs-2.0/README.md | 2 +- docs-2.0/graph-computing/nebula-algorithm.md | 2 +- .../about-exchange/ex-ug-limitations.md | 18 - .../about-exchange/ex-ug-what-is-exchange.md | 30 ++ .../parameter-reference/ex-ug-parameter.md | 23 +- .../use-exchange/ex-ug-import-from-jdbc.md | 379 ++++++++++++++++++ docs-2.0/nebula-spark-connector.md | 2 +- .../replication-between-clusters.md | 206 ++++++++-- mkdocs.yml | 12 +- 20 files changed, 643 insertions(+), 126 deletions(-) rename docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/{upgrade-nebula-from-200-to-latest.md => upgrade-nebula-from-300-to-latest.md} (75%) create mode 100644 docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index ae29818190e..6649785b9c9 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -2,7 +2,7 @@ name: Publish docs via GitHub Pages on: push: branches: - - v3.1.0 + - v3.1.3 jobs: deploy: @@ -10,7 +10,7 @@ jobs: steps: - uses: actions/checkout@v2 with: - fetch-depth: 0 # fetch all commits/branches for gitversion + fetch-depth: 1 # fetch all commits/branches for gitversion - name: Setup Python uses: actions/setup-python@v1 @@ -24,12 +24,12 @@ jobs: - name: Git Config run: git config user.name whitewum && git config user.email min.wu@vesoft.com - - name: Mike Deploy 3.1.0 + - name: Mike Deploy 3.1.3 run: | - # mike delete v3.1.0 -p + # mike delete v3.1.3 -p git fetch origin gh-pages --depth=1 # fix mike's CI update mike list - mike deploy 3.1.0 -p --rebase + mike deploy 3.1.3 -p --rebase mike list # - name: Deploy diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md index c4d6bc7940c..8c340ec8e3d 100644 --- a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md +++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md @@ -80,7 +80,7 @@ Graphs consist of vertices and edges. Nebula Graph uses key-value pairs to store - The storage structure of vertices - Different from Nebula Graph version 2.x, version 3.x added a new key for each vertex. Compared to the old key that still exists, the new key has no `TagID` field and no value. Vertices in Nebula Graph can now live without tags owing to the new key. + Different from Nebula Graph version 2.x, version 3.x added a new key for each vertex. Compared to the old key that still exists, the new key has no `TagID` field and no value after enabling the configuration without tag. Vertices in Nebula Graph can now live without tags owing to the new key. ![The vertex structure of Nebula Graph](https://docs-cdn.nebula-graph.com.cn/figures/3.0-vertex-key.png) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index e8fe089c7ec..fca3de8a2d9 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -277,7 +277,7 @@ By nGQL, you CAN NOT directly getting all the vertices without specifying the ta E.g., You CAN NOT run `MATCH (n) RETURN (n)`. An error like `Scan vertices or edges need to specify a limit number, or limit number can not push down.` will be returned. -You can use [Nebula Algorithm](../nebula-algorithm.md). +You can use [Nebula Algorithm](../graph-computing/nebula-algorithm.md). Or get vertices by each tag, and then group them by yourself. @@ -301,7 +301,7 @@ This is a very slow operation to get the out/in degree since no accelaration can There is no such command. -You can use [Nebula Algorithm](../nebula-algorithm.md). +You can use [Nebula Algorithm](../graph-computing/nebula-algorithm.md). ## About operation and maintenance diff --git a/docs-2.0/20.appendix/6.eco-tool-version.md b/docs-2.0/20.appendix/6.eco-tool-version.md index 567671deacb..2c475fc7921 100644 --- a/docs-2.0/20.appendix/6.eco-tool-version.md +++ b/docs-2.0/20.appendix/6.eco-tool-version.md @@ -108,7 +108,7 @@ Nebula Flink Connector is a connector that helps Flink users quickly access Nebu ## Nebula Algorithm -Nebula Algorithm (Algorithm for short) is a Spark application based on [GraphX](https://spark.apache.org/graphx/), which uses a complete algorithm tool to analyze data in the Nebula Graph database by submitting a Spark task To perform graph computing, use the algorithm under the lib repository through programming to perform graph computing for DataFrame. For details, see [What is Nebula Algorithm](../nebula-algorithm.md). +Nebula Algorithm (Algorithm for short) is a Spark application based on [GraphX](https://spark.apache.org/graphx/), which uses a complete algorithm tool to analyze data in the Nebula Graph database by submitting a Spark task To perform graph computing, use the algorithm under the lib repository through programming to perform graph computing for DataFrame. For details, see [What is Nebula Algorithm](../graph-computing/nebula-algorithm.md). |Nebula Graph version|Algorithm version| |:---|:---| @@ -116,7 +116,7 @@ Nebula Algorithm (Algorithm for short) is a Spark application based on [GraphX]( ## Nebula Analytics -Nebula Analytics is an application that integrates the open-source Plato Graph Computing Framework, with which Nebula Analytics performs graph computations on Nebula Graph database data. For details, see [What is Nebula Analytics](../nebula-analytics.md). +Nebula Analytics is an application that integrates the open-source Plato Graph Computing Framework, with which Nebula Analytics performs graph computations on Nebula Graph database data. For details, see [What is Nebula Analytics](../graph-computing/nebula-analytics.md). |Nebula Graph version|Analytics version| |:---|:---| diff --git a/docs-2.0/20.appendix/learning-path.md b/docs-2.0/20.appendix/learning-path.md index 266c578e22c..55d21614cbe 100644 --- a/docs-2.0/20.appendix/learning-path.md +++ b/docs-2.0/20.appendix/learning-path.md @@ -81,7 +81,7 @@ This topic is for anyone interested in learning more about Nebula Graph. You can | ------------------------------------------------------------ | | [Upgrade Nebula Graph to {{nebula.branch}}](../4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md) | - + ### 3.3 Configure Nebula Graph diff --git a/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md b/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md index d3723d412fb..b356b33e579 100644 --- a/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md +++ b/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md @@ -4,12 +4,16 @@ A vertex can have one or more tags. -- If a vertex has only one tag, the vertex will become a vertex without tag. +- If a vertex has only one tag, the vertex **CANNOT** be accessed after you drop it. The vertex will be dropped in the next compaction. But its edges are available, this operation will result in dangling edges. - If a vertex has multiple tags, the vertex is still accessible after you drop one of them. But all the properties defined by this dropped tag **CANNOT** be accessed. This operation only deletes the Schema data. All the files or directories in the disk will not be deleted directly until the next compaction. +!!! Compatibility + + In NebulaGraph {{nebula.release}}, inserting vertex without tag is not supported by default. If you want to use the vertex without tags, add `--graph_use_vertex_key=true` to the configuration files (`nebula-graphd.conf`) of all Graph services in the cluster, and add `--use_vertex_key=true` to the configuration files (`nebula-storaged.conf`) of all Storage services in the cluster. + ## Prerequisites - Running the `DROP TAG` statement requires some [privileges](../../7.data-security/1.authentication/3.role-list.md) for the graph space. Otherwise, Nebula Graph throws an error. diff --git a/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md b/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md index bf6caf718ee..d526fd926f3 100644 --- a/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md +++ b/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md @@ -48,14 +48,14 @@ prop_value_list: !!! Note - - `IF NOT EXISTS` only compares the names of the VID and the tag (excluding properties). - - `IF NOT EXISTS` will read to check whether the data exists, which will have a significant impact on performance. + - `IF NOT EXISTS` only compares the names of the VID and the tag (excluding properties). + - `IF NOT EXISTS` will read to check whether the data exists, which will have a significant impact on performance. -* `tag_name` denotes the tag (vertex type), which must be created before `INSERT VERTEX`. For more information, see [CREATE TAG](../10.tag-statements/1.create-tag.md). +- `tag_name` denotes the tag (vertex type), which must be created before `INSERT VERTEX`. For more information, see [CREATE TAG](../10.tag-statements/1.create-tag.md). - !!! caution + !!! Compatibility - Nebula Graph {{ nebula.release }} supports inserting vertices without tags. + In NebulaGraph {{nebula.release}}, inserting vertex without tag is not supported by default. If you want to use the vertex without tags, add `--graph_use_vertex_key=true` to the configuration files (`nebula-graphd.conf`) of all Graph services in the cluster, add `--use_vertex_key=true` to the configuration files (`nebula-storaged.conf`) of all Storage services in the cluster. An example of a command to insert a vertex without tag is `INSERT VERTEX VALUES "1":();`. * `prop_name_list` contains the names of the properties on the tag. @@ -76,9 +76,6 @@ Examples are as follows. ## Examples ```ngql -# Insert a vertex without tag. -nebula> INSERT VERTEX VALUES "1":(); - # The following examples create tag t1 with no property and inserts vertex "10" with no property. nebula> CREATE TAG IF NOT EXISTS t1(); nebula> INSERT VERTEX t1() VALUES "10":(); diff --git a/docs-2.0/3.ngql-guide/6.functions-and-expressions/4.schema.md b/docs-2.0/3.ngql-guide/6.functions-and-expressions/4.schema.md index 4d1c4e21c5b..ca8cfe3b303 100644 --- a/docs-2.0/3.ngql-guide/6.functions-and-expressions/4.schema.md +++ b/docs-2.0/3.ngql-guide/6.functions-and-expressions/4.schema.md @@ -38,8 +38,8 @@ Nebula Graph supports the following schema functions. |string type() | Returns the edge type of an edge.| |src()|Returns the source vertex ID of an edge. The data type of the result is the same as the vertex ID.| |dst()|Returns the destination vertex ID of an edge. The data type of the result is the same as the vertex ID.| -|vertex startNode() | Visits an edge or a path and returns its source vertex ID.| -|string endNode() | Visits an edge or a path and returns its destination vertex ID.| +|string startNode() | Visits a path and returns its information of source vertex ID, including VIDs, tags, properties, and values.| +|string endNode() | Visits a path and returns its information of destination vertex ID, including VIDs, tags, properties, and values.| |int rank() | Returns the rank value of an edge.| ## Examples diff --git a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-300-to-latest.md similarity index 75% rename from docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md rename to docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-300-to-latest.md index da8b66fca9f..f4eb06b3307 100644 --- a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md +++ b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-300-to-latest.md @@ -1,10 +1,7 @@ -# Upgrade Nebula Graph v2.0.x to v{{nebula.release}} +# Upgrade Nebula Graph v3.x to v{{nebula.release}} -To upgrade Nebula Graph v2.0.x to v{{nebula.release}}, you only need to use the RPM/DEB package of v{{nebula.release}} for the upgrade, or [compile it](../2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md) and then reinstall. +To upgrade NebulaGraph v3.x to v{{nebula.release}}, you only need to use the RPM/DEB package of v{{nebula.release}} for the upgrade, or [compile it](../2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md) and then reinstall. -!!! note - - Nebula Graph v2.0.x refers to v2.0.0-GA and v2.0.1 releases. If your Nebula Graph version is too low (v2.0.0-RC, v2.0.0-beta, v1.x), see [Upgrade Nebula Graph to v{{nebula.release}}](upgrade-nebula-graph-to-latest.md). ## Upgrade steps with RPM/DEB packages @@ -12,6 +9,10 @@ To upgrade Nebula Graph v2.0.x to v{{nebula.release}}, you only need to use the 2. Stop all Nebula Graph services. For details, see [Manage Nebula Graph Service](../../2.quick-start/5.start-stop-service.md). It is recommended to back up the configuration file before updating. + !!! caution + + If you want to use the vertex without tags, add `--graph_use_vertex_key=true` to the configuration files (`nebula-graphd.conf`) of all Graph services in the cluster, add `--use_vertex_key=true` to the configuration files (`nebula-storaged.conf`) of all Storage services in the cluster. + 3. Execute the following command to upgrade: - RPM package diff --git a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md index 1b73de26141..1d8c17e30e9 100644 --- a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md +++ b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md @@ -127,45 +127,12 @@ To upgrade Nebula Graph from historical versions to {{nebula.release}}: !!! note If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). -5. Use the new db_upgrader file in the `bin` directory to upgrade the format of old data. - - !!! danger - This step DOES NOT back up the Storage data. To avoid data loss, before executing this step, make sure that you have followed the **Preparations before the upgrade** section and backed up the Meta data and Storage data. - - Command syntax: - - ``` - /bin/db_upgrader \ - --src_db_path= \ - --dst_db_path= \ - --upgrade_meta_server=:[, : ...] \ - --upgrade_version=2:3 - ``` - - - `old_storage_data_path` indicates the path of the Storage data. It is defined by the `data_path` parameter in the Storage configuration files. - - `data_backup_path` indicates a custom path for data backup. **This option does not work for the current version and the old data will not be backed up to any path.** - - `meta_server_ip` and `port` indicate the IP address and port number of a Meta server. - - `2:3` indicates that the upgrade is from version 2.x to 3.x. - - Example for the test in this topic: - - ``` - /bin/db_upgrader \ - --src_db_path=/usr/local/nebula/data/storage \ - --dst_db_path=/home/vesoft/nebula/data-backup \ - --upgrade_meta_server=192.168.8.132:9559 \ - --upgrade_version=2:3 - ``` - - !!! note - If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). - -6. Start all the Graph and Storage services. +5. Start all the Graph and Storage services. !!! note If the operation fails, stop the upgrade and ask for help on [the forum](https://discuss.nebula-graph.com.cn/) or [GitHub](https://github.com/vesoft-inc/nebula/issues). -7. Connect to the new version of Nebula Graph to verify that services are available and data are complete. For how to connect, see [Connect to Nebula Graph](../connect-to-nebula-graph.md). +6. Connect to the new version of Nebula Graph to verify that services are available and data are complete. For how to connect, see [Connect to Nebula Graph](../connect-to-nebula-graph.md). Currently, there is no official way to check whether the upgrade is successful. You can run the following reference statements to test the upgrade: diff --git a/docs-2.0/8.service-tuning/3.system-design.md b/docs-2.0/8.service-tuning/3.system-design.md index 65ed519687b..f8abfbbc5d7 100644 --- a/docs-2.0/8.service-tuning/3.system-design.md +++ b/docs-2.0/8.service-tuning/3.system-design.md @@ -4,7 +4,7 @@ - Nebula Graph {{ nebula.release }} is good at handling small requests with high concurrency. In such scenarios, the whole graph is huge, containing maybe trillions of vertices or edges, but the subgraphs accessed by each request are not large (containing millions of vertices or edges), and the latency of a single request is low. The concurrent number of such requests, i.e., the QPS, can be huge. -- On the other hand, in interactive analysis scenarios, the request concurrency is usually not high, but the subgraphs accessed by each request are large, with thousands of millions of vertices or edges. To lower the latency of big requests in such scenarios, you can split big requests into multiple small requests in the application, and concurrently send them to multiple graphd processes. This can decrease the memory used by each graphd process as well. Besides, you can use [Nebula Algorithm](../nebula-algorithm.md) for such scenarios. +- On the other hand, in interactive analysis scenarios, the request concurrency is usually not high, but the subgraphs accessed by each request are large, with thousands of millions of vertices or edges. To lower the latency of big requests in such scenarios, you can split big requests into multiple small requests in the application, and concurrently send them to multiple graphd processes. This can decrease the memory used by each graphd process as well. Besides, you can use [Nebula Algorithm](../graph-computing/nebula-algorithm.md) for such scenarios. -There is no tool specially designed to show the real-time status and overall progress of the synchronization for now. diff --git a/mkdocs.yml b/mkdocs.yml index a69630e25de..bddc6a8ab34 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -9,7 +9,7 @@ repo_url: 'https://github.com/vesoft-inc/nebula-docs' copyright: Copyright © 2022 Nebula Graph # modify -edit_uri: 'edit/v3.1.0/docs-2.0/' +edit_uri: 'edit/v3.1.3/docs-2.0/' theme: name: material @@ -76,7 +76,6 @@ plugins: - CHANGELOG.md - spark-connector/* - 4.deployment-and-installation/5.zone.md - - 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md - nebula-cloud/nebula-cloud-on-azure/azure-fully-managed/* - nebula-cloud.md @@ -88,7 +87,7 @@ plugins: - with-pdf: copyright: 2022 Vesoft Inc. - cover_subtitle: 3.1.0 + cover_subtitle: 3.1.3 author: Min Wu, Yao Zhou, Cooper Liang, Foesa Yang, Abby Huang cover: true back_cover: true @@ -122,13 +121,13 @@ extra: - icon: 'fontawesome/brands/github' link: 'https://github.com/vesoft-inc/nebula-docs' nebula: - release: 3.1.0 + release: 3.1.3 nightly: nightly master: master base20: 2.0 base200: 2.0.0 branch: release-3.1 - tag: v3.1.0 + tag: v3.1.3 studio: release: 3.3.2 tag: v3.3.0 @@ -425,7 +424,7 @@ nav: # - Manage zone: 4.deployment-and-installation/5.zone.md - Upgrade: - Upgrade Nebula Graph to the latest version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md -# - Upgrade Nebula Graph from v2.0.x to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md +# - Upgrade Nebula Graph from v2.0.x to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-300-to-latest.md - Uninstall Nebula Graph: 4.deployment-and-installation/4.uninstall-nebula-graph.md - Configurations and logs: @@ -627,6 +626,7 @@ nav: - Import data from MaxCompute: nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md - Import data from Pulsar: nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md - Import data from Kafka: nebula-exchange/use-exchange/ex-ug-import-from-kafka.md + - Import data from JDBC: nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md - Import data from SST files: nebula-exchange/use-exchange/ex-ug-import-from-sst.md - Export data from Nebula Graph: nebula-exchange/use-exchange/ex-ug-export-from-nebula.md - Exchange FAQ: nebula-exchange/ex-ug-FAQ.md From bca302d031a9edca6fbc0d513601c61880f4cdef Mon Sep 17 00:00:00 2001 From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:14:53 +0800 Subject: [PATCH 2/3] update --- docs-2.0/20.appendix/release-note.md | 96 ++++++++++++++-------------- 1 file changed, 47 insertions(+), 49 deletions(-) diff --git a/docs-2.0/20.appendix/release-note.md b/docs-2.0/20.appendix/release-note.md index fcf54e5c9f0..3aa4de00071 100644 --- a/docs-2.0/20.appendix/release-note.md +++ b/docs-2.0/20.appendix/release-note.md @@ -1,57 +1,55 @@ # Nebula Graph {{ nebula.release }} release notes -## Enhancement - -- Patterns can now be used in `WHERE` statements. For example: `MATCH (v:player) WHERE (v)-[:like]->() RETURN v`. [#3997](https://github.com/vesoft-inc/nebula/pull/3997) -- `CLEAR SPACE` can be used to clear graph space and index data, but the graph space schema and index names are reserved. [#3989](https://github.com/vesoft-inc/nebula/pull/3989) -- The vertex alias can be repeated in match patterns, like `MATCH (v)-->(v)`. [#3929](https://github.com/vesoft-inc/nebula/pull/3929) -- Optimized `SUBGRAPH` and `FIND PATH` for better performance. [#3871](https://github.com/vesoft-inc/nebula/pull/3871) [#4095](https://github.com/vesoft-inc/nebula/pull/4095) -- Optimized query paths to reduce redundant paths and time complexity.[4126](https://github.com/vesoft-inc/nebula/pull/4162) -- Optimized the method to get properties for better performance of `MATCH` statements. [#3750](https://github.com/vesoft-inc/nebula/pull/3750) -- Optimized `GO` and `YIELD` clauses to avoid extracting redundant properties. [#3974](https://github.com/vesoft-inc/nebula/pull/3974) -- Support for filter and limit pushdown when getting properties. [3844](https://github.com/vesoft-inc/nebula/pull/3844) [3839](https://github.com/vesoft-inc/nebula/pull/3839) -- `maxHop` is optional in MATCH variable-length paths.[#3881](https://github.com/vesoft-inc/nebula/pull/3881) -- Graph spaces are physically deleted after using `DROP SPACE`. [#3913](https://github.com/vesoft-inc/nebula/pull/3913) -- Optimized number parsing in date time, date, time. [#3797](https://github.com/vesoft-inc/nebula/pull/3797) -- Added the `toSet` function which converts `LIST` or `SET` to `SET`. [#3594](https://github.com/vesoft-inc/nebula/pull/3594) -- nGQL statements can be used to display the HTTP port of Nebula Graph services and the HTTP2 port has been disabled. [#3808](https://github.com/vesoft-inc/nebula/pull/3808) -- The number of sessions for connections to each graphd with the same client IP and the same user is limited. [#3729](https://github.com/vesoft-inc/nebula/pull/3729) -- Optimized the waiting mechanism to ensure a timely connection to the metad after the storaged starts. [#3971](https://github.com/vesoft-inc/nebula/pull/3971) -- When a node has multiple paths and an error of the disk corresponding to a particular path occurs, it is no longer to rebuild the node. [#4131](https://github.com/vesoft-inc/nebula/pull/4131) -- Optimized the job manager. [#3976](https://github.com/vesoft-inc/nebula/pull/3976) [#4045](https://github.com/vesoft-inc/nebula/pull/4045) [#4001](https://github.com/vesoft-inc/nebula/pull/4001) -- The `DOWNLOAD` and `INGEST` SST files are now managed with the job manager. [#3994](https://github.com/vesoft-inc/nebula/pull/3994) -- Support for error code display when a job fails. [#4067](https://github.com/vesoft-inc/nebula/pull/4067) -- The OS page cache can be disabled and the block cache and Nebula Graph storage cache can only be used in a shared environment, to avoid memory usage interference between applications. [#3890](https://github.com/vesoft-inc/nebula/pull/3890) -- Updated the default value of the KV separation threshold from 0 to 100. [#3879](https://github.com/vesoft-inc/nebula/pull/3879) -- Support for using gflag to set the upper limit of expression depth for a better fit of different machine environments. [#3722](https://github.com/vesoft-inc/nebula/pull/3722) -- Added a permission check for `KILL QUERY`. When the authorization is enabled, the GOD user can kill any query and the users with other roles can only kill queries that they own. [#3896](https://github.com/vesoft-inc/nebula/pull/3896) -- Support for more complier launchers, including distcc and sccache. [#3896](https://github.com/vesoft-inc/nebula/pull/3896) -- More dumping tables are supported with the meta dump tool. [#3870](https://github.com/vesoft-inc/nebula/pull/3870) -- The storage layer controls the concurrency of write operations (INSERT VERTEX or EDGE) from reporting an error and requiring a client retry to using the internal queueing mechanism. [#3926](https://github.com/vesoft-inc/nebula/pull/3926) +## Changes -## Bugfix +- Vertex without tag is not supported by default. If you want to use the vertex without tags, add --graph_use_vertex_key=true to the configuration files (nebula-graphd.conf) of all Graph services in the cluster, and add --use_vertex_key=true to the configuration files (nebula-storaged.conf) of all Storage services in the cluster. + +## Enhancement + +- Support to show the status of [synchronize between two clusters]((../synchronization-and-migration/replication-between-clusters.md)). + +- Enhanced memory usage of `AtomicLogBuffer` to avoid OOM problems when rebuilding indexes and data synchronization. -- Fixed the crash when using a function call as part of a filter in a `LOOKUP` statement. [#4111](https://github.com/vesoft-inc/nebula/pull/4111) -- Fixed the crash when there were non-indexed properties in an `IN` clause. [#3986](https://github.com/vesoft-inc/nebula/pull/3986) -- Fixed the storage service crash when concurrently scanning vertices and edges. [#4190](https://github.com/vesoft-inc/nebula/pull/4190) -- Fixed the crash when performing aggregation queries with patterns in a `MATCH` statement. [#4180](https://github.com/vesoft-inc/nebula/pull/4180) -- Fixed the crash when getting the JSON results of a `profile` query. [#3998](https://github.com/vesoft-inc/nebula/pull/3998) -- Fixed the crash when the `async` interface in the Lambda function finished running and the task in `threadManager` was not executed. [#4000](https://github.com/vesoft-inc/nebula/pull/4000) -- Fixed the `GROUP BY` output bug. [#4128](https://github.com/vesoft-inc/nebula/pull/4128) -- Fixed the bug that the version wasn't displayed with `SHOW HOSTS` sometimes. [#4116](https://github.com/vesoft-inc/nebula/pull/4116) -- Fixed the bug on parameters for `id(n) == $var`, `id(n) IN [$var]`, `id(n) == $var.foo.bar`, and `id(n) IN $var.foo.bar`. [#4024](https://github.com/vesoft-inc/nebula/pull/4024) -- Fixed the bug that an incorrect path direction occurred in `MATCH...WHERE`. [#4091](https://github.com/vesoft-inc/nebula/pull/4091) -- Fixed the bug that the result of referencing multiple `MATCH` variables in a `WHERE` clause was incorrect. [#4143](https://github.com/vesoft-inc/nebula/pull/4143) -- Fixed the optimizer bug. [#4146](https://github.com/vesoft-inc/nebula/pull/4146) -- Fixed the bug that the storage service failed to handle Raft snapshots. [#4019](https://github.com/vesoft-inc/nebula/pull/4019) -- Fixed the bug that the storage service would not accept more logs after receiving a snapshot. [#3909](https://github.com/vesoft-inc/nebula/pull/3909) -- Fixed the bug that snapshots did not contain the vertices without tags. [#4189](https://github.com/vesoft-inc/nebula/pull/4189) -- Fixed the latest schema version read failure when the schema version is greater than 255. [#4023](https://github.com/vesoft-inc/nebula/pull/4023) -- Fixed the bug that `SHOW STATS` did not count the vertices that had no tags. [#3967](https://github.com/vesoft-inc/nebula/pull/3967) -- Fixed the bug that the timestamp was fetched incorrectly sometimes. [#3958](https://github.com/vesoft-inc/nebula/pull/3958) -- Fixed the bug that the `root` user could be granted with other roles in the graph space. [#3868](https://github.com/vesoft-inc/nebula/pull/3868) -- Fixed the duplicate count of column indexes in the lexical parser bug. [#3626](https://github.com/vesoft-inc/nebula/pull/3626) +- Unify the configuration file. + +- Adjust the level of heartbeat log. + +## Bugfix +- Fixed the crash of web service when receiving some special attack messages. +- Fixed the crash on dropping full-text index. +- Fixed the crash of map concurrency. +- Fixed the crash of raft in certain cases. +- Fixed the storage service crash when the length of the VID in a vertex or edge deletion statement exceeds the defined length on an indexed base. +- Fixed the crash that caused by a wrong expression syntax. +- Fixed the crash of `LOOKUP`. +- Fixed the crash of complex `MATCH`. +- ixed the crash in the optimization phase of multiple `MATCH`. +- Fixed the crash of variable types collected. +- Fixed the crash that caused by a illegal expression. +- Fixed the bug that storage would hang when there is only space path but no part path. +- Fixed the deadlock of leader balance job executor. +- Fixed the infinite loop when building balance plan. +- Fixed the bug of rebuild full-text index failure. +- Fixed the bug of using logrotate. +- Fixed the bug that the machine key is lost when restoring. +- Fixed the bug that the host can't stop when canceling the future of snapshot. +- Fixed the bug of cache size overflow and dead lock. +- Fixed the bug of missing `RETURN` clause in MetaDaemon. +- Fixed the split brain in raft. +- Fixed the bug that the meta listener validated license. +- Fixed the bug that the meta listener didn't clean data. +- Fixed the bug of drainer sync dirty data. +- Fixed the bug that the drainer daemon can't exit normally. +- Fixed the bug to keep audit log async available. +- Fixed the concurrent exception of multiple `MATCH`. +- Fixed the bug that the rebuild tag index task could not be re-executed properly. +- Fixed the bug that rebuild tag index job always failed after stopping a running job. +- Fixed the bug that the ElasticSearch writing error caused by truncation of UTF8 characters. +- Fixed the bug to remove truncate text before write into ElasticSearch. +- Fixed the bug when using ElasticSearch for audit log, the audit logs of DML and DQL types are not recorded. +- Fixed the bug where the service could not be started if the log directory did not exist when `ENABLE_BREAKPAD` was enabled. +- Fixed the bug that If there is a GOD which name is not root, the root user will be created when meta init. ## Legacy versions From 152f8c7158a89626db20b5ed144fe41464cf0441 Mon Sep 17 00:00:00 2001 From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Date: Tue, 29 Nov 2022 10:20:45 +0800 Subject: [PATCH 3/3] update --- docs-2.0/20.appendix/release-note.md | 38 ++++++++++++++-------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/docs-2.0/20.appendix/release-note.md b/docs-2.0/20.appendix/release-note.md index 3aa4de00071..4ae96361296 100644 --- a/docs-2.0/20.appendix/release-note.md +++ b/docs-2.0/20.appendix/release-note.md @@ -12,44 +12,44 @@ - Unify the configuration file. -- Adjust the level of heartbeat log. +- Adjust the level of the heartbeat log. ## Bugfix - Fixed the crash of web service when receiving some special attack messages. -- Fixed the crash on dropping full-text index. +- Fixed the crash on dropping the full-text index. - Fixed the crash of map concurrency. - Fixed the crash of raft in certain cases. - Fixed the storage service crash when the length of the VID in a vertex or edge deletion statement exceeds the defined length on an indexed base. -- Fixed the crash that caused by a wrong expression syntax. +- Fixed the crash caused by a wrong expression syntax. - Fixed the crash of `LOOKUP`. - Fixed the crash of complex `MATCH`. -- ixed the crash in the optimization phase of multiple `MATCH`. +- Fixed the crash in the optimization phase of multiple `MATCH`. - Fixed the crash of variable types collected. -- Fixed the crash that caused by a illegal expression. -- Fixed the bug that storage would hang when there is only space path but no part path. +- Fixed the crash caused by an illegal expression. +- Fixed the bug that storage would hang when there is only the space path but no part path. - Fixed the deadlock of leader balance job executor. -- Fixed the infinite loop when building balance plan. -- Fixed the bug of rebuild full-text index failure. +- Fixed the infinite loop when building a balance plan. +- Fixed the bug of rebuilding full-text index failure. - Fixed the bug of using logrotate. - Fixed the bug that the machine key is lost when restoring. -- Fixed the bug that the host can't stop when canceling the future of snapshot. -- Fixed the bug of cache size overflow and dead lock. -- Fixed the bug of missing `RETURN` clause in MetaDaemon. -- Fixed the split brain in raft. -- Fixed the bug that the meta listener validated license. +- Fixed the bug that the host can't stop when canceling the future of the snapshot. +- Fixed the bug of cache size overflow and deadlock. +- Fixed the bug of missing the `RETURN` clause in MetaDaemon. +- Fixed the split brain in the raft. +- Fixed the bug that the meta listener validated the license. - Fixed the bug that the meta listener didn't clean data. -- Fixed the bug of drainer sync dirty data. +- Fixed the bug of the drainer syncing dirty data. - Fixed the bug that the drainer daemon can't exit normally. -- Fixed the bug to keep audit log async available. +- Fixed the bug to keep the audit log async available. - Fixed the concurrent exception of multiple `MATCH`. - Fixed the bug that the rebuild tag index task could not be re-executed properly. -- Fixed the bug that rebuild tag index job always failed after stopping a running job. +- Fixed the bug that the rebuild tag index job always failed after stopping a running job. - Fixed the bug that the ElasticSearch writing error caused by truncation of UTF8 characters. -- Fixed the bug to remove truncate text before write into ElasticSearch. -- Fixed the bug when using ElasticSearch for audit log, the audit logs of DML and DQL types are not recorded. +- Fixed the bug to remove the truncated text before writing into ElasticSearch. +- Fixed the bug when using ElasticSearch for audit logs, the audit logs of DML and DQL types are not recorded. - Fixed the bug where the service could not be started if the log directory did not exist when `ENABLE_BREAKPAD` was enabled. -- Fixed the bug that If there is a GOD which name is not root, the root user will be created when meta init. +- Fixed the bug that If there is a GOD whose name is not root, the root user will be created when meta init. ## Legacy versions