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

Problems with fetching added metadata to a file #1368

Closed
kad-willej opened this issue Sep 23, 2022 · 1 comment · Fixed by #1369
Closed

Problems with fetching added metadata to a file #1368

kad-willej opened this issue Sep 23, 2022 · 1 comment · Fixed by #1369
Labels

Comments

@kad-willej
Copy link

Problem:

When I add metadata to a file, it will correctly store the metadata but incorrectly retrieve the metadata.

Fetch by:

    minioClient.listObjects(
                    ListObjectsArgs.builder()
                            .bucket(properties.getBucket())
                            .recursive(true)
                            .prefix(prefixUrl)
                            .includeUserMetadata(true)
                            .build()

Result from returned Item object:

userMetadata = {Metadata@10820} 
 map = {Collections$UnmodifiableMap@10823}  size = 3
  "Value" -> "A4"
  "Items" -> null
  "Key" -> "X-Amz-Meta-Pdftype"

The key should be "X-Amz-Meta-Pdftype" and not "Key", and result should be "A4". This seems malformed, I'm not sure if this is caused by the SDK, since it seem to happen with the upgrade of Minio server.

Tried versions (with Docker):
minio.RELEASE.2022-07-04T21-02-54Z <- Works
minio.RELEASE.2022-08-26T19-53-15Z <- Fails

So even though the problem appears with the change of the Minio server instead of the SDK, I upload the issue here as well since it happens when using the SDK.

@balamurugana
Copy link
Member

As you have mentioned, if server upgrade makes the failure, its nothing to do with minio-java

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants