vesoft-inc / vesoft-inc/nebula-java
remove the cache in meta client
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- Java
- Stars
- 199
- Forks
- 125
- Avg merge
- 5h 6m
- Merged PRs (30d)
- 3
Description
MetaManager is a cache info for nebula meta, but in client, the schema info will not be read many times, and the cache does not make mush sense.
Besides, if the leader info changed in nebula server, the cache will not know it and will not update, which keeps the old and wrong meta info.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing MetaManager and the client paths that read schema and leader metadata. Confirm how cached information becomes stale, then verify that removing the cache makes the client use current Nebula Meta information without retaining old schema or leader data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100