Correct the date filter check for batch replication #20569
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.
Description
The condition were incorrect as we were comparing the filter value against the modification time object.
For example if created after filter date is after modification time of object, that means object was created before the filter time and should be skipped while replication because as per the filter we need only the objects created after the filter date.
Motivation and Context
How to test this PR?
mc anonymous set public ALIAS/BUCKETmc cpto first instance's bucketMtimevalue using curl command (for i in {1..20}; do curl -X PUT -k "https://minio2:9010/test-bucket/shu$i" -d @/etc/issue -H "X-Minio-Source-Mtime: 2013-03-12T16:19:03.115209866-08:00"; done)createdBeforefilterTypes of changes
Checklist:
commit-idorPR #here)