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
S3Select EventStream closes prematurely #3202
Comments
Hi @garry-9590, thanks for reaching out to us. This seems like an issue with the service ending the stream prematurely rather than something specific to the AWS SDK for Go. I'll be reaching out to the S3 team internally about this, once I have more information I'll update the issue accordingly. |
Hi @diehlaws thank you for responding. Please do let me know when you have new information on this issue. |
Unfortunately I have been unable to reproduce the described behavior on my end. I generated a CSV file with 200-byte records of random data and have consistently received an End Event before my code completes, however I have not been successful in printing the data in the source CSV file using the provided code. Can you provide the The S3 team has requested the following information as they have also been unable to reproduce this behavior using a 1GB CSV file.
They also noted that exceeding S3's limits should result in 503 responses rather than an unexpected EOF. |
Please fill out the sections below to help us address your issue.
Version of AWS SDK for Go?
1.25.17 & 1.29.22
Version of Go (
go version
)?1.13.6
What issue did you see?
Please refer to the code below. The issue I am observing is that after processing some of the rows of csv, "ALL DONE" is getting printed while "End Event received" is not printed in the output logs. This means that the for loop over the stream of events was exited without encountering an EndEvent.
As a result, the PipeWriter gets closed without sending out an EOF error and the PipeReader loop is never exited and it keeps on throwing unexpectedEOF errors because the PipeWriter is closed.
I am trying to ingest 100,000 records of 200bytes each.
Is there a limitation on how much data EventStream can process?
Steps to reproduce
Same issue was reported on an earlier version (#2769)
If you have an runnable example, please include it.
The text was updated successfully, but these errors were encountered: