-
Notifications
You must be signed in to change notification settings - Fork 0
[improve][pulsar-testclient] Add disableBatching as CLI argument for pulsar-perf-producer #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
|
||
| @Parameter(names = { "-db", | ||
| "--disable-batching" }, description = "Disable batching if true") | ||
| public boolean disableBatching = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default value is false. you don't need extra assignment for boolean.
| } | ||
| }); | ||
|
|
||
| Consumer<byte[]> newConsumer1 = pulsarClient.newConsumer().topic(topic).subscriptionName("sub-2") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't have to publish or consume message. somehow, we need to assert that Producer is created with batching-disable option. you can also use reflection if any variable is private and you have to find the value of that field.
|
The pr had no activity for 30 days, mark with Stale label. |
Motivation
The pulsar-perf-tool should be able to take "disableBatching" as an input argument as it can be provided by the user.
Modifications
Add an extra parameter to in the PerformanceProducer.java class.
Extract producerBuilder creation into a separate method.
Add unit testcase to verify if batching is disabled
Verifying this change
This change added tests and can be verified as follows:
-Added unit test to verify functionality with batching disabled
Does this pull request potentially affect one of the following parts:
If
yeswas chosen, please highlight the changesDocumentation
Check the box below or label this PR directly.
Need to update docs?
doc-required(Your PR needs to update docs and you will update later)
doc-not-needed(Please explain why)
doc(Your PR contains doc changes)
doc-complete(Docs have been already added)