[ 
https://issues.apache.org/jira/browse/CAMEL-22049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-22049.
--------------------------------------
    Resolution: Fixed

> camel-aws2-kinesis: use created async client for KCL consumer
> -------------------------------------------------------------
>
>                 Key: CAMEL-22049
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22049
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws2-kinesis
>    Affects Versions: 4.x
>            Reporter: Marco Carletti
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.10.5, 4.12.0
>
>
> Since the 
> [Kinesis2Endpoint|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws2-kinesis/src/main/java/org/apache/camel/component/aws2/kinesis/Kinesis2Endpoint.java#L68]
>  already manages the instance of the _kinesisAsyncClient_ it would be nice to 
> use this instance instead of to create a new one to bind to the registry due 
> to the override of the [consumer 
> configuration|https://github.com/apache/camel/blob/main/components/camel-aws/camel-aws2-kinesis/src/main/java/org/apache/camel/component/aws2/kinesis/KclKinesis2Consumer.java#L88]
>  that always use the configured client (even if it is null)
> currently the endpoint
> {code:none}
> aws2-kinesis://mydatastream?region=myregion&useKclConsumers=true&asyncClient=true&useDefaultCredentialsProvider=true{code}
> won't work without an instance of a 
> _software.amazon.awssdk.services.kinesis.KinesisAsyncClient_ in the registry 
> configured even if the camel component will create one



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to