-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[improve][io] Add support for the complete KinesisProducerConfiguration in KinesisSinkConfig #24489
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
Conversation
dlg99
left a comment
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.
LGTM
|
Could you rebase to master so that the checkstyle check for tests will be applied? |
29b330a to
e6f01d7
Compare
@BewareMyPower |
|
/pulsarbot rerun-failure-checks |
|
It's weird for this failure: @sandeep-mst maybe you have to try merging to master again to re-trigger the build. BTW, @lhotari do you have any idea about the failure above? |
…ducerConfiguration hashmap.
4d76453 to
f609773
Compare
|
@BewareMyPower |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #24489 +/- ##
============================================
+ Coverage 73.57% 74.33% +0.76%
- Complexity 32624 32933 +309
============================================
Files 1877 1869 -8
Lines 139502 146105 +6603
Branches 15299 16762 +1463
============================================
+ Hits 102638 108610 +5972
+ Misses 28908 28889 -19
- Partials 7956 8606 +650
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@BewareMyPower, @dlg99, @lhotari The OWASP dependency check is failing on master as well and I have verified that Let me know if anything else is required on this PR. |
@BewareMyPower yes. Retrying a failed build after 3 days won't work since the GitHub workflow artifacts retention is set to 3 days so that we don't overflow the size of storage. It's necessary to trigger a completely new build in that case. Usually it's recommended to merge master to the PR branch to trigger that. |
…on in KinesisSinkConfig (apache#24489) (cherry picked from commit 80902f8)
…on in KinesisSinkConfig (apache#24489) (cherry picked from commit 80902f8)
…on in KinesisSinkConfig (apache#24489) (cherry picked from commit 80902f8)
…on in KinesisSinkConfig (apache#24489) (cherry picked from commit 80902f8)
…on in KinesisSinkConfig (apache#24489) (cherry picked from commit 80902f8)
…on in KinesisSinkConfig (#24489)
…on in KinesisSinkConfig (apache#24489)
…on in KinesisSinkConfig (apache#24489)
Fixes #24422
Motivation
The Apache Pulsar KinesisSink utilises the KinesisProducer from the KPL. The KPL provides a comprehensive set of configuration parameters through its KinesisProducerConfiguration class.
In the current KinesisSink implementation, most of these parameters such as collectionMaxCount, collectionMaxSize, connectTimeout, maxConnections, and minConnections—are not configurable. This restricts users' ability to optimise the sink's performance, or meet network and operational requirements potentially affecting throughput, latency, and resource utilisation.
Modifications
Verifying this change
(Please pick either of the following options)
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository:
cognitree#25