Support DynamoDB BillingMode propagation from Ruby to Java.
Bump KCL version to 1.14.3
What does this PR do?
It allows to set DynamoDB BillingMode from pipeline yaml config's additional_settings map.
As BillingMode in Java can not be casted from String or Int to BillingMode on the fly we have to cast it manually before passing from Ruby to Java.
Why is it important/What is the impact to the user?
This PR gives an opportunity to tune one additional setting of Kinesis Client and avoid erroneous behavior.
Behavior before changes:
[ERROR] 2023-01-09 07:31:49.865 [[main]-pipeline-manager] javapipeline - Pipeline error {:pipeline_id=>"main", :exception=>#<TypeError: cannot convert instance of class org.jruby.RubyString to class com.amazonaws.services.dynamodbv2.model.BillingMode>...
KCL version's bump keeps plugin updated.
Checklist
[+] My code follows the style guidelines of this project
[+] I have commented my code, particularly in hard-to-understand areas
[-] I have made corresponding changes to the documentation
[-] I have made corresponding change to the default configuration files (and/or docker env variables)
[-] I have added tests that prove my fix is effective or that my feature works
[enhancement]
Release notes
What does this PR do?
It allows to set DynamoDB BillingMode from pipeline yaml config's
additional_settings
map. As BillingMode in Java can not be casted from String or Int to BillingMode on the fly we have to cast it manually before passing from Ruby to Java.Why is it important/What is the impact to the user?
This PR gives an opportunity to tune one additional setting of Kinesis Client and avoid erroneous behavior.
Behavior before changes:
KCL version's bump keeps plugin updated.
Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs