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

Fix bug where s3 scan could skip when lastModifiedTimestamps are the same #4124

Merged
merged 1 commit into from
Feb 14, 2024

Conversation

graytaylor0
Copy link
Member

@graytaylor0 graytaylor0 commented Feb 13, 2024

Description

Provides some overlap of a second when filtering out objects based on lastmodified timestamp for subsequent scans. This filtering is done to lower the amount of lookups required to source coordination, and will not result in duplicate processing if there are any objects that are returned to source coordinator twice.

Issues Resolved

Resolves #4123

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

…same

Signed-off-by: Taylor Gray <tylgry@amazon.com>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

@graytaylor0 graytaylor0 merged commit a8024e9 into opensearch-project:main Feb 14, 2024
47 checks passed
@graytaylor0 graytaylor0 deleted the S3ScanFix branch February 14, 2024 17:07
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.6 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.6 2.6
# Navigate to the new working tree
cd .worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-4124-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a8024e99aa4ff0b0d7de86d642fdac14cf1da58d
# Push it to GitHub
git push --set-upstream origin backport/backport-4124-to-2.6
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.6

Then, create a pull request where the base branch is 2.6 and the compare/head branch is backport/backport-4124-to-2.6.

graytaylor0 added a commit to graytaylor0/data-prepper that referenced this pull request Feb 14, 2024
…same (opensearch-project#4124)

Signed-off-by: Taylor Gray <tylgry@amazon.com>
(cherry picked from commit a8024e9)
graytaylor0 added a commit to graytaylor0/data-prepper that referenced this pull request Feb 14, 2024
graytaylor0 added a commit that referenced this pull request Feb 14, 2024
…same (#4124) (#4127)

Signed-off-by: Taylor Gray <tylgry@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] S3 Scan has potential to filter out objects with the same timestamp
3 participants