chore: add docker using / add load data methods#13
chore: add docker using / add load data methods#13Ethereal-O wants to merge 3 commits intohugegraph:masterfrom
Conversation
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Walkthrough扩展 HugeGraph Vermeer 快速入门文档：新增三种运行方案（Docker Compose、docker run、源码构建）与三种数据加载方式（本地、HugeGraph、HDFS），并补充了配置示例、REST API 请求示例与安全说明。 Changes
Sequence Diagram(s)sequenceDiagram
participant User as 用户
participant CLI as 启动方式（compose/run/源码）
participant Vermeer as Vermeer REST API
participant Loader as 加载组件
participant Source as 数据来源（本地 / HugeGraph / HDFS）
rect rgb(240,248,255)
User->>CLI: 启动服务（compose/run/源码）
CLI->>Vermeer: 启动并注册服务
end
Note right of Vermeer: 创建计算任务并选择加载方法
User->>Vermeer: POST /tasks (含 load.type)
alt load.type == local
Vermeer->>Loader: 请求读取本地文件（路径/格式）
Loader->>Source: 读取本地文件系统
else load.type == hugegraph
Vermeer->>Loader: 请求从 HugeGraph 拉取（含凭证）
Loader->>Source: 调用 HugeGraph REST API
else load.type == hdfs
Vermeer->>Loader: 请求读取 HDFS 路径
Loader->>Source: 访问 HDFS
end
Loader-->>Vermeer: 返回数据准备状态
Vermeer->>User: 返回任务创建响应与计算/输出状态
预估代码审查工作量🎯 2 (Simple) | ⏱️ ~5–15 分钟
诗
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello @Ethereal-O, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the documentation for HugeGraph Vermeer by introducing detailed guides for Docker-based deployment, offering both Docker Compose and Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
@codecov-ai-reviewer review |
This comment has been minimized.
This comment has been minimized.
![codecov-ai[bot]](https://avatars.githubusercontent.com/in/797565?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds documentation for running Vermeer using Docker and introduces methods for loading data from HugeGraph and HDFS. The changes are applied to both the Chinese and English versions of the quickstart guide.
My review focuses on improving the clarity and consistency of the new documentation. I've suggested using more generic placeholders in the Docker examples and standardizing the JSON formatting in the data loading examples for better readability. These changes will help users follow the instructions more easily.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
content/en/docs/quickstart/computing/hugegraph-vermeer.md (2)
19-23: Docker Compose 卷挂载路径可能无法正确扩展第21行的
~/:/go/bin/config使用了 Shell 主目录扩展符号~，但在docker-compose.yaml中可能不会被正确解析。建议明确使用绝对路径示例，或说明需要在运行前手动替换。- Modify the volume in `docker-compose.yaml`, for example, changing the two instances of `~/:/go/bin/config` to `/home/user/config:/go/bin/config` (or your own configuration directory). + Modify the volume in `docker-compose.yaml`, for example, changing the two instances of `~/:/go/bin/config` to an absolute path like `/home/user/config:/go/bin/config` (or your own configuration directory). Note: `~` may not be expanded in docker-compose.yaml.
57-69: 工作目录与 CONFIG_DIR 示例路径需要澄清第60行的
CONFIG_DIR=/home/ethereal/config使用了非常具体的用户路径，容易造成用户困惑。建议改为通用示例或添加说明用户应替换为自己的配置路径。同时，第21行和第60行的路径处理方式不一致（一个相对路径示例，一个绝对路径）。- CONFIG_DIR=/home/ethereal/config + # Set to your configuration directory absolute path + CONFIG_DIR=/path/to/your/configcontent/cn/docs/quickstart/computing/hugegraph-vermeer.md (2)
57-70: 将示例配置路径改为通用占位符。第60行使用了具体用户名
/home/ethereal/config，应改为通用的占位符，便于用户根据实际情况替换。建议修改为：
- CONFIG_DIR=/home/ethereal/config + CONFIG_DIR=/path/to/your/config或提供更多示例说明用户应如何替换路径。
146-162: 将示例 IP 地址改为通用占位符。第154行的 IP 地址
10.14.139.69:8686是具体的内部网络地址，应改为通用占位符便于用户根据实际环境替换。建议修改示例：
- "load.hg_pd_peers": "[\"10.14.139.69:8686\"]", + "load.hg_pd_peers": "[\"your_hugegraph_host:8686\"]",同时建议在文档中补充说明 PD 服务地址的格式要求。
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md(3 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)
🔇 Additional comments (3)
content/en/docs/quickstart/computing/hugegraph-vermeer.md (2)
101-103: 工作节点命名约定不一致第103行中提到
./vermeer --env=worker01，但前面的 Docker 示例（第79行）使用的是--env=worker。请澄清工作节点命名约定是使用worker还是worker01或其他格式，并保证整个文档的一致性。
120-189: 三种数据加载方法文档结构清晰，JSON 格式正确新增的三种数据加载方法（本地文件、HugeGraph、HDFS）的文档结构良好，每个方法都有详细的请求示例。JSON 格式验证无误，参数文档清晰。建议参考 Vermeer 参数列表文档的链接是否存在或是否需要更新。
content/cn/docs/quickstart/computing/hugegraph-vermeer.md (1)
1-5: 综合评价：文档结构清晰，内容全面。整体而言，此次更新为 Vermeer 快速开始指南增加了重要的内容：
- 三种部署方案清晰完整
- 三种数据加载方式详细示例
- 16 个算法示例规范一致
主要改进建议已在其他评论中详细说明。
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the HugeGraph Vermeer documentation by adding comprehensive deployment instructions and data loading methods. The changes provide users with multiple deployment options and expand the documentation to cover additional data loading sources beyond local files.
Key Changes:
- Added three deployment methods: Docker Compose (recommended), standalone Docker run with custom networking, and source code compilation
- Extended data loading documentation to include HugeGraph and HDFS loading methods alongside the existing local file loading
- Standardized formatting of request examples for better clarity
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| content/en/docs/quickstart/computing/hugegraph-vermeer.md | Added English documentation for three deployment options and two new data loading methods (HugeGraph and HDFS) with complete configuration examples |
| content/cn/docs/quickstart/computing/hugegraph-vermeer.md | Added Chinese documentation mirroring the English version, providing deployment instructions and expanded data loading methods |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md (1)
548-548: 修复第3.14 全图Kout示例中的语法错误。第548行使用了中文逗号（，）而不是JSON逗号，导致JSON格式错误：
"compute.max_step":"2"，应该是"compute.max_step":"2",。应用以下修复：
"compute.algorithm": "kout_all", "compute.parallel":"10", "output.type":"local", "output.parallel":"10", "output.file_path":"result/kout", -"compute.max_step":"2"， +"compute.max_step":"2", "compute.filter":"risk_level==1"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)
🧰 Additional context used
🪛 LanguageTool
content/en/docs/quickstart/computing/hugegraph-vermeer.md
[style] ~21-~21: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... your project directory. If not, you'll need to create one based on the project's docke...
(REP_NEED_TO_VB)
🔇 Additional comments (4)
content/en/docs/quickstart/computing/hugegraph-vermeer.md (2)
19-107: Approve Docker deployment documentation.The three deployment options are well-documented with clear prerequisites, permissions guidance, and consistent path usage. The addition of prerequisite notes (line 21) and permissions hints (line 45) addresses previous review concerns effectively. The progression from recommended (Compose) to manual (docker run) to source-based builds is logical and helpful.
124-144: Approve local file loading example.The "Load from Local Files" example is clear and provides good context for users. JSON formatting is consistent here.
content/cn/docs/quickstart/computing/hugegraph-vermeer.md (2)
19-107: 认可Docker部署文档。三种部署方案文档完整清晰，包含了必要的前置条件说明（第21行）和权限指导（第45行）。从推荐方案（Docker Compose）到手动方式（docker run）再到源码构建的递进安排合理且易于用户选择。
126-144: 认可本地文件加载示例。"从本地加载"示例清晰明了，为用户提供了良好的上下文。此部分的JSON格式一致。
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (7)
content/cn/docs/guides/toolchain-local-test.md (2)
196-196: 语法改进 - 第 196 行建议调整措辞。当前: "在与
docker-compose.yml相同的目录下创建"建议改为: "在与
docker-compose.yml相同的目录下创建" → "在docker-compose.yml相同的目录下创建"
1-445: 整体质量良好 - 此新指南提供了全面的工具链本地测试文档，涵盖部署、环境配置和故障排查。考虑补充关于处理敏感凭证（如密码和密钥）的专门安全注意事项，与第 2.1 节（HugeGraph Server 鉴权配置）中的密码设置示例保持一致。AGENTS.md (2)
17-17: 格式改进 - 第 17 行建议使用 Markdown 链接格式而非裸 URL。当前:
Download from: https://github.com/gohugoio/hugo/releases建议:
Download from: [GitHub Releases](https://github.com/gohugoio/hugo/releases)
160-170: 使用标题而非强调 - 第 160、164、168 行使用**Error:**等强调格式作为小标题不符合 Markdown 最佳实践。建议改为###标题。示例：
-**Error: "TOCSS: failed to transform scss/main.scss"** +### Error: "TOCSS: failed to transform scss/main.scss" -Cause: Using standard Hugo instead of Hugo Extended -Solution: Install Hugo Extended version +**Cause:** Using standard Hugo instead of Hugo Extended + +**Solution:** Install Hugo Extended versioncontent/en/docs/guides/toolchain-local-test.md (2)
293-294: 安全提示 - 第 293-294 行的 curl 认证示例应加上明确说明这些是测试用凭证。建议补充注释：# Note: 'admin:pa' are test-only default credentials; never use real credentials in documentation curl -u admin:pa http://localhost:8080/graphs
1-444: 整体质量良好 - 此英文版本与中文版本相对应，提供了全面的工具链本地测试指南。建议在第 5 节（常见问题）中补充关于敏感信息处理的专门部分。content/en/docs/quickstart/computing/hugegraph-vermeer.md (1)
19-95: ✓ Docker Compose 部分质量良好 - 配置示例完整，包括网络设置和卷挂载。建议在第 72-75 行补充说明卷挂载权限的注意事项（与第 98 行的权限说明保持一致）。- **Volume**: For example, change both instances of `~/:/go/bin/config` to `/home/user/config:/go/bin/config`. - **Note**: Ensure the host directory has appropriate permissions (e.g., `chmod 755`) for the Docker process to access.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (4)
content/cn/docs/images/toolchain-test-mermaid-1.pngis excluded by!**/*.pngcontent/cn/docs/images/toolchain-test-mermaid-2.pngis excluded by!**/*.pngcontent/en/docs/images/toolchain-test-mermaid-1.pngis excluded by!**/*.pngcontent/en/docs/images/toolchain-test-mermaid-2.pngis excluded by!**/*.png
📒 Files selected for processing (21)
.github/workflows/auto-pr-review.yml(1 hunks).gitignore(1 hunks)AGENTS.md(1 hunks)content/cn/docs/guides/backup-restore.md(1 hunks)content/cn/docs/guides/faq.md(1 hunks)content/cn/docs/guides/security.md(1 hunks)content/cn/docs/guides/toolchain-local-test.md(1 hunks)content/cn/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)content/cn/docs/quickstart/toolchain/_index.md(1 hunks)content/cn/docs/quickstart/toolchain/hugegraph-hubble.md(1 hunks)content/cn/docs/quickstart/toolchain/hugegraph-loader.md(1 hunks)content/cn/docs/quickstart/toolchain/hugegraph-tools.md(1 hunks)content/en/docs/guides/backup-restore.md(1 hunks)content/en/docs/guides/faq.md(1 hunks)content/en/docs/guides/security.md(1 hunks)content/en/docs/guides/toolchain-local-test.md(1 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)content/en/docs/quickstart/toolchain/_index.md(1 hunks)content/en/docs/quickstart/toolchain/hugegraph-hubble.md(1 hunks)content/en/docs/quickstart/toolchain/hugegraph-loader.md(1 hunks)content/en/docs/quickstart/toolchain/hugegraph-tools.md(1 hunks)
✅ Files skipped from review due to trivial changes (10)
- content/en/docs/guides/backup-restore.md
- content/cn/docs/guides/security.md
- content/cn/docs/quickstart/toolchain/hugegraph-hubble.md
- content/en/docs/quickstart/toolchain/hugegraph-tools.md
- content/cn/docs/guides/faq.md
- content/en/docs/guides/faq.md
- content/en/docs/guides/security.md
- content/en/docs/quickstart/toolchain/_index.md
- content/cn/docs/guides/backup-restore.md
- content/cn/docs/quickstart/toolchain/hugegraph-loader.md
🚧 Files skipped from review as they are similar to previous changes (1)
- content/cn/docs/quickstart/computing/hugegraph-vermeer.md
🧰 Additional context used
🪛 Gitleaks (8.28.0)
content/en/docs/guides/toolchain-local-test.md
[high] 293-294: Discovered a potential basic authorization token provided in a curl command, which could compromise the curl accessed resource.
(curl-auth-user)
🪛 LanguageTool
content/cn/docs/guides/toolchain-local-test.md
[uncategorized] ~196-~196: 您的意思是“在"于"”吗？
Context: ... datanode_data: ``` #### Hadoop 配置挂载 在与 docker-compose.yml 相同的目录下创建 `./config...
(YU7_YU8)
AGENTS.md
[uncategorized] ~124-~124: The official name of this software platform is spelled with a capital “H”.
Context: ...The site uses GitHub Actions for CI/CD (.github/workflows/hugo.yml): 1. Triggers:...
(GITHUB)
content/en/docs/guides/toolchain-local-test.md
[uncategorized] ~443-~443: The official name of this software platform is spelled with a capital “H”.
Context: ...egraph-server/) * CI Script Path: .github/workflows/*-ci.yml (CI configuration f...
(GITHUB)
🪛 markdownlint-cli2 (0.18.1)
content/cn/docs/guides/toolchain-local-test.md
267-267: Hard tabs
Column: 2
(MD010, no-hard-tabs)
AGENTS.md
17-17: Bare URL used
(MD034, no-bare-urls)
160-160: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
164-164: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
168-168: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (7)
content/cn/docs/quickstart/toolchain/_index.md (1)
6-7: ✓ 批准 - 工具链测试指南的参考链接添加正确。.gitignore (1)
21-30: ✓ 批准 - AI 代理配置文件的忽略规则设置合理，保持 AGENTS.md 作为真实来源。content/cn/docs/quickstart/toolchain/hugegraph-tools.md (1)
11-11: ✓ 批准 - 工具链测试指南的参考链接合理地插入到适当位置。content/en/docs/quickstart/computing/hugegraph-vermeer.md (2)
106-112: ✓ 批准网络配置说明 - docker run 部分清晰地解释了自定义网桥网络的创建和静态 IP 分配。网络配置文档充分。
176-220: ✓ 三种加载方法的结构清晰 - 本地文件、HugeGraph 和 HDFS 三种方式的说明和示例都很完整。第 202 行的安全警告（不在配置文件中存储真实密码）是重要的改进。content/en/docs/quickstart/toolchain/hugegraph-hubble.md (1)
14-14: 确保Testing Guide链接与其他工具链文档保持一致。该文件添加的Testing Guide注释与
hugegraph-loader.md中的改动模式相同，都指向/docs/guides/toolchain-local-test。此一致性很好，但需要确保该链接目标文件确实存在（请参考对hugegraph-loader.md文件的验证请求）。content/en/docs/quickstart/toolchain/hugegraph-loader.md (1)
22-22: Testing Guide链接验证通过，无需修改。已确认文件
content/en/docs/guides/toolchain-local-test.md存在，Testing Guide中引用的链接/docs/guides/toolchain-local-test有效，不会产生断链。新增的注释内容正确引导用户查看本地测试文档，改动无误。
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md (1)
212-213: 修复 JSON 格式中冒号后的空格不一致。JSON 示例中冒号后的空格不统一。具体问题：
- 第212-213行：
"load.hugegraph_username":"admin",和"load.hugegraph_password":"xxxxx",冒号后缺少空格- 第233行：
"load.hdfs_conf_path": "/path/to/conf",冒号后有两个空格- 其他字段（如第211、214-215行等）：冒号后正确使用单个空格
为保持格式一致，所有字段应使用
"key": "value"的格式（冒号后跟单个空格）。建议修复：
"params": { "load.parallel": "50", "load.type": "hugegraph", "load.hg_pd_peers": "[\"<your-hugegraph-ip>:8686\"]", "load.hugegraph_name": "DEFAULT/hugegraph2/g", - "load.hugegraph_username":"admin", - "load.hugegraph_password":"xxxxx", + "load.hugegraph_username": "admin", + "load.hugegraph_password": "xxxxx", "load.use_out_degree": "1", "load.use_outedge": "1" }并将第233行修改为：
- "load.hdfs_conf_path": "/path/to/conf", + "load.hdfs_conf_path": "/path/to/conf",Also applies to: 233-233
🧹 Nitpick comments (3)
content/en/docs/quickstart/computing/hugegraph-vermeer.md (1)
106-112: 添加网络创建的说明注释虽然代码中创建了自定义桥接网络，但缺少对其目的和必要性的解释。建议在网络创建命令前添加注释，说明 master 和 worker 容器必须在同一网络上才能通信。
建议在第 106 行前添加以下注释：
+ # 创建自定义桥接网络以启用 master 和 worker 容器之间的通信 + # 注意：两个容器必须在同一网络上才能正常运行 docker network create --driver bridge \ --subnet 172.20.0.0/24 \ vermeer_networkcontent/cn/docs/quickstart/computing/hugegraph-vermeer.md (2)
196-245: 改进 HDFS 加载参数文档的清晰度。HDFS 加载示例（第220-245行）中的参数说明可以进一步完善。虽然已经使用了通用占位符（如
/path/to/conf），但仍缺少关键信息：
load.hdfs_namenode：第232行示例"name_node1:9000"很好，但应说明是hostname:port格式load.hdfs_conf_path和load.krb_conf_path：应明确说明是否接受相对路径或只支持绝对路径load.vertex_files和load.edge_files：应说明是否支持通配符（例如hdfs:///data/graph/vertices/*）以及路径格式要求建议在示例下方补充参数说明表或注释，帮助用户正确配置这些参数。
200-201: 确认安全警告位置是否最优。第200行添加的安全警告
⚠️ 很好，但位置可以更优化。目前警告仅在「从hugegraph加载」示例前显示，但「从hdfs加载」示例（第220行）中的"load.krb_name":"xxxxx"参数也涉及敏感凭证。建议：
- 在「从hdfs加载」示例前也添加类似警告，或
- 在第170-173行的「加载图数据」总体介绍中添加通用的安全警告，适用于所有加载方法
这样可以确保所有涉及凭证的示例都有清晰的安全提示。
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(2 hunks)
🔇 Additional comments (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md (2)
47-47: 缺少配置路径说明的具体指导。第47行和57行注释建议用户修改
~/:/go/bin/config为自己的配置路径，但第72行示例中显示/home/user/config。需要说明：
- 配置文件应该放在何处（例如是否应该是项目根目录的
config文件夹）- 用户是否需要提前创建这个目录
- 如果没有配置文件应该如何处理
建议在第72行处补充说明，指导用户正确准备配置目录。
Also applies to: 57-57
94-147: 缺少端口映射和服务访问说明。docker run 示例中（第94-147行）没有配置端口映射。根据 2.2 节的加载示例，任务需要访问
http://localhost:8688/tasks/create，但本节的 docker run 命令没有说明：
- Master 和 Worker 需要暴露哪些端口？
- 如何通过
-p参数进行端口映射？- 8688 端口是在配置文件中指定还是默认端口？
建议补充端口映射的说明和示例，例如在 Master 的 docker run 命令中添加
-p 8688:8688。
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md(3 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md
267-267: Hard tabs
Column: 2
(MD010, no-hard-tabs)
content/en/docs/quickstart/computing/hugegraph-vermeer.md
269-269: Hard tabs
Column: 2
(MD010, no-hard-tabs)
There was a problem hiding this comment.
Actionable comments posted: 3
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
content/cn/docs/quickstart/computing/hugegraph-vermeer.md(3 hunks)content/en/docs/quickstart/computing/hugegraph-vermeer.md(3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- content/cn/docs/quickstart/computing/hugegraph-vermeer.md
2 participants
Purpose of the PR
Summary by CodeRabbit
文档更新