Added a method to filter out "ghost" objects GCS started to create #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VOvchinnikov
changed the title
VOvchinnikov
force-pushed
the
patch-google-ghost-objects
branch
from
8fc6b5b
to
053b956
Compare
artgra
approved these changes
Sep 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We suddenly found that each actual object and even directories in GCS now have these nameless 0-sized files accompanying them. This messes up the compliance with filesystem protocols, e.g. by returning extra items in the
lsresults.The commit is constructed to add an extra filter for such objects for page items processing.