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

AWS SQS Consume fetches record in a weird format #360

Open
shrutimantri opened this issue Jan 28, 2024 · 1 comment
Open

AWS SQS Consume fetches record in a weird format #360

shrutimantri opened this issue Jan 28, 2024 · 1 comment
Labels
area/backend Needs backend code changes area/plugin Plugin-related issue or feature request bug Something isn't working good first issue Great issue for new contributors

Comments

@shrutimantri
Copy link
Contributor

Expected Behavior

AWS SQS Consume should be able to fetch the rows from the SQS queue, and have the fetched records noted as a single column with 1 record per row.

Actual Behaviour

The records are fetched from the SQS queue as 1 record per row, but each character in the record is put in a separate column. I have attached the screenshot for better understanding.

Screenshot 2024-01-28 at 6 49 43 PM

Steps To Reproduce

  1. Use the sample flow as mentioned in the page with appropriate access key, secret key and queueUrl. Also add maxRecords to the flow.
  2. Produce records in the queue (equal or more than the number of maxrRecords).
  3. Execute the flow.

Environment Information

  • Kestra Version: 0.13.8
  • Plugin version: 0.13.8
  • Operating System (OS / Docker / Kubernetes): Docker
  • Java Version (If not docker):

Example flow

id: "consume"
type: "io.kestra.plugin.aws.sqs.Consume"
accessKeyId: "<access-key>"
secretKeyId: "<secret-key>"
region: "eu-central-1"
queueUrl: "https://sqs.eu-central-1.amazonaws.com/000000000000/test-queue"
maxRecords: 2
@shrutimantri shrutimantri added the bug Something isn't working label Jan 28, 2024
@anna-geller anna-geller added this to the v0.18.0 milestone Jan 29, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Issues Jun 10, 2024
@anna-geller anna-geller removed this from the v0.18.0 milestone Jul 3, 2024
@smunteankestra
Copy link

fails with
image

@smunteankestra smunteankestra removed their assignment Jul 3, 2024
@anna-geller anna-geller added area/backend Needs backend code changes area/plugin Plugin-related issue or feature request labels Aug 15, 2024
@tchiotludo tchiotludo added good first issue Great issue for new contributors and removed kind/good-first-issue labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes area/plugin Plugin-related issue or feature request bug Something isn't working good first issue Great issue for new contributors
Projects
Status: Backlog
Development

No branches or pull requests

4 participants