BenchReadThroughputLatency support config the way of gen ledger path. #4219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In BenchReadThroughputLatency, it generates the ledger zk node path using
String.format("/ledgers/L%010d", ledger.get());
But if the user uses
HierarchicalLedgerManager
,LegacyHierarchicalLedgerManager
, orLongHierarchicalLedgerManager
, the ledger zk node path is not the same as the way in the BenchReadThroughputLatency.So we need support config the
genLedgerWay
to match the custom LedgerManager.