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
ListObjects V2 causes endless loop when > 1000 items #1703
Comments
@half-life666 what is your server implementation here? |
oh, it's huawei obs, do you think that's the problem? |
yes they do not implement ListObjectsV2 API or they do and implement it incorrectly - they need to send back ContinuationToken if they do not we have no way to know. This is not our SDK bug. However we can try to error out when such broken implementations are seen in the wild. |
Thanks for pointing that out! |
This SDK is only meant to work with AWS S3 and its compatible implementations such as MinIO. It is out of our scope for us to support obscure implementations such as Huawei OBS. But to catch such actors we will error out when necessary conditions are not met. |
error out when pointing to incomplete/broken S3 compatible implementations during ListObjectsV2(). Huawei OBS seems to be broken, error out. Ref minio#1703 for more information.
error out when pointing to incomplete/broken S3 compatible implementations during ListObjectsV2(). Huawei OBS seems to be broken, error out. Ref #1703 for more information.
I use below code on a prefix which have > 1000 objects, it will loop forever on first 1000 objects:
I saw there is #719 but it seems only add a validation and does not seem fix this issue.
On java sdk there is minio/minio-java#580 which seems fixed the issue for v2, but go sdk still have this problem.
listobject v1 works fine though.
The text was updated successfully, but these errors were encountered: