-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix bug related to wrong state.ID in awss3 direct s3 input #32164
fix bug related to wrong state.ID in awss3 direct s3 input #32164
Conversation
…not-read-the-file-from-s3-input-occasionally-leading-to-no-data-getting-generated-weekly
Adding @andrewkroh as a reviewer since I see he's done a lot of work on this input in the past. |
…-input-occasionally-leading-to-no-data-getting-generated-weekly
This pull request is now in conflicts. Could you fix it? 🙏
|
…-input-occasionally-leading-to-no-data-getting-generated-weekly
@andrewkroh good to merge? |
This pull request is now in conflicts. Could you fix it? 🙏
|
…-input-occasionally-leading-to-no-data-getting-generated-weekly
* fix bug related to wrong state.ID in awss3 direct s3 input * changelog * fix everywhere * fix everywhere * fix race in benchmark * fix race in benchmark * more linting * introduce stateID function (cherry picked from commit 7e7755c) # Conflicts: # x-pack/filebeat/input/awss3/input_benchmark_test.go # x-pack/filebeat/input/awss3/states_test.go
* fix bug related to wrong state.ID in awss3 direct s3 input * changelog * fix everywhere * fix everywhere * fix race in benchmark * fix race in benchmark * more linting * introduce stateID function (cherry picked from commit 7e7755c)
…rect s3 input (#32288) * fix bug related to wrong state.ID in awss3 direct s3 input (#32164) * fix bug related to wrong state.ID in awss3 direct s3 input * changelog * fix everywhere * fix everywhere * fix race in benchmark * fix race in benchmark * more linting * introduce stateID function (cherry picked from commit 7e7755c) # Conflicts: # x-pack/filebeat/input/awss3/input_benchmark_test.go # x-pack/filebeat/input/awss3/states_test.go * fix conflict Co-authored-by: Andrea Spacca <andrea.spacca@elastic.co>
…2164) (elastic#32289) * fix bug related to wrong state.ID in awss3 direct s3 input * changelog * fix everywhere * fix everywhere * fix race in benchmark * fix race in benchmark * more linting * introduce stateID function (cherry picked from commit 7e7755c) Co-authored-by: Andrea Spacca <andrea.spacca@elastic.co>
* fix bug related to wrong state.ID in awss3 direct s3 input * changelog * fix everywhere * fix everywhere * fix race in benchmark * fix race in benchmark * more linting * introduce stateID function
Bug
What does this PR do?
Fix a bug related to using to different ID values when comparing states of s3 objects in order to skip them in the awss3 s3 direct input
Why is it important?
When an S3 object in a bucket get updated we will skip it otherwise, instead of ingesting the new content
Checklist
- [ ] 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 filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs