docs(ufs): document s3.list_objects_version parameter for S3 mounts#70
Merged
lzjqsdd merged 1 commit intoJun 29, 2026
Merged
Conversation
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Document the new
s3.list_objects_versionmount parameter in the UFS user manual, alongside the existing S3 parameters.v2(default) uses ListObjects V2. Set tov1for buckets that are incompatible with V2 listing — notably Baidu BOS, which returnsIsTruncated=truewithout aNextContinuationToken, making the V2 lister loop forever so the mount appears to hang. V1 listing uses the last object key as the marker and works around such services.Documents the option added in CurvineIO/curvine#936. Follows the same location/style as #66 (
s3.force.path.style).