vesoft-inc / vesoft-inc/nebula-java

The storage leader address for the partition of metaManager cache does not look correct

Open
#354 3 comments 2 reactions 1 assignee View on GitHub

@Nicole00 is already working on this.

Since Dec 29, 2022.

good first issue type/enhancement type/question
Dominant language
Java
Stars
199
Forks
125
Avg merge
5h 6m
Merged PRs (30d)
3

Description

对应代码:https://github.com/vesoft-inc/nebula-java/blob/3518faa8444c1f590fba92d7f7c66946ad696852/client/src/main/java/com/vesoft/nebula/client/meta/MetaManager.java#L114

GetPartsAllocReq返回的分区信息无法确定哪个host是leader吧?代码取了第一个,对比 ListHosts 返回的 LeaderParts,第一个并不是 Leader Host。我是参考这里的 https://github.com/vesoft-inc/nebula-common/blob/master/src/common/clients/meta/MetaClient.cpp#L3189

另外 StorageClient 目前只有 scanXXX 接口,有无计划补全剩下的接口?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.