Skip to content

[ISSUE #257]Use thread name as rocksdb path#256

Merged
ni-ze merged 4 commits intoapache:developfrom
ni-ze:develop
Jan 20, 2023
Merged

[ISSUE #257]Use thread name as rocksdb path#256
ni-ze merged 4 commits intoapache:developfrom
ni-ze:develop

Conversation

@ni-ze
Copy link
Copy Markdown
Contributor

@ni-ze ni-ze commented Jan 20, 2023

  1. use the name of thread as rocksdb path;
  2. clean the temporary data of rocksdb in local;
  3. make WorkerThread shutdown method idempotent;

close #257

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Jan 20, 2023

Codecov Report

Merging #256 (45f24e3) into develop (f499b19) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           develop    #256   +/-   ##
=======================================
  Coverage     0.00%   0.00%           
=======================================
  Files           79      79           
  Lines         2640    2646    +6     
  Branches       250     252    +2     
=======================================
- Misses        2640    2646    +6     
Impacted Files Coverage Δ
.../apache/rocketmq/streams/core/common/Constant.java 0.00% <ø> (ø)
...he/rocketmq/streams/core/running/WorkerThread.java 0.00% <0.00%> (ø)
...ache/rocketmq/streams/core/state/RocksDBStore.java 0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@ni-ze ni-ze changed the title Use thread name as rocksdb path [ISSUE #257]Use thread name as rocksdb path Jan 20, 2023
@ni-ze ni-ze merged commit 51d13d5 into apache:develop Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use thread name as rocksdb path

2 participants