Single Pull Request or Multiple Pull Requests for Similar Fixes

[LucasEby]

I found a similar issue in the 7 different test methods below. I have fixed the problems in my fork already. Since each of these tests are inside completely different areas of the code base, would you prefer for me to submit a single PR with all of the tests fixed inside of it (Option A) or separate PR's for each fix (Option B)?

Files modified (along with some pom.xmls):

• org.apache.pulsar.common.policies.data.NamespaceOwnershipStatusTest#testSerialization
• org.apache.pulsar.common.policies.impl.NamespaceIsolationPoliciesTest#testJsonSerialization
• org.apache.pulsar.functions.utils.FunctionConfigUtilsTest#testConvertBackFidelity
• org.apache.pulsar.functions.utils.SinkConfigUtilsTest#testConvertBackFidelity
• org.apache.pulsar.functions.utils.SourceConfigUtilsTest#testBatchConfigMergeEqual
• org.apache.pulsar.io.elasticsearch.ElasticSearchExtractTest#testGenericRecord
• org.apache.pulsar.io.kinesis.UtilsTest#testKeyValueSerializeNoValue.

[lhotari]

@LucasEby For fixing similar issues across multiple tests, a single PR makes sense.

[lhotari]

Thank you for contributing to Apache Pulsar. If you're interested in contributing by fixing flaky tests, the list of flaky tests can be found at https://github.com/apache/pulsar/issues?q=is%3Aissue%20state%3Aopen%20flaky. We have a lot of them.
Please also join the #dev channel in the community Slack, where you can reach out to me and other developers when you have any questions about contributions or need reviews. Sometimes PR reviews get delayed, and it's necessary to remind others to review them.
The contribution guide is available at https://pulsar.apache.org/contribute/. In Apache projects, the developer mailing list is used to discuss and make official project decisions. Please also subscribe to the dev mailing list if you'd like to also get involved in project decisions.

[LucasEby]

Sounds great, thank you! I plan to look into the already open issues for flaky tests soon.