Skip to content
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

Add parameter to configure maxMessagesPerPoll for in aws-sqs-source Kemelet #2118

Closed
jakubmalek opened this issue Jul 19, 2024 · 4 comments
Closed
Assignees
Milestone

Comments

@jakubmalek
Copy link
Contributor

The {{Sqs2Endpoint}} can be configured with maxMessagesPerPoll parameter, which is translated into the maxNumberOfMessages parameter for the AWSA SQS client.
The aws-sqs-source Kamelet should be extended to support configuration is this parameter.

It should also be possible to configure the visibilityTimeout and waitTimeSeconds parameters.

@oscerd oscerd self-assigned this Jul 19, 2024
@oscerd oscerd added this to the 4.8.0 milestone Jul 19, 2024
@oscerd
Copy link
Contributor

oscerd commented Jul 19, 2024

This will go in 4.8.0 and so it will be in the next CKC 4.8.0 LTS release.

jakubmalek added a commit to jakubmalek/camel-kamelets that referenced this issue Jul 19, 2024
@jakubmalek
Copy link
Contributor Author

@oscerd I've already opened a PR to add those parameters :)

@oscerd
Copy link
Contributor

oscerd commented Jul 19, 2024

Great!

@oscerd
Copy link
Contributor

oscerd commented Jul 19, 2024

I'll review later

jakubmalek added a commit to jakubmalek/camel-kamelets that referenced this issue Jul 22, 2024
oscerd pushed a commit that referenced this issue Jul 22, 2024
* aws-sqs-source Kamelet extended with `maxMessagesPerPoll`, `waitTimeSeconds` and `visibilityTimeout` parameters (#2118)

* Fixed aws-sqs-source parameter descriptions and tests (#2118)
@oscerd oscerd closed this as completed Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants