[
https://issues.apache.org/jira/browse/JCLOUDS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032536#comment-14032536
]
Adrian Cole commented on JCLOUDS-391:
-------------------------------------
Here's an example of the patch approach:
@Override
public String putBlob(String container, Blob blob, PutOptions options) {
if (options.isMultipart()) {
String result = multipartUploadStrategy.get().execute(container, blob);
if (result != null) {
sync.setBlobMetadata(container, blob.getMetadata().getName(),
blob.getMetadata().getUserMetadata());
}
}
return putBlob(container, blob);
}
> can't set user-defined metadata for Azure with multipart blobs
> --------------------------------------------------------------
>
> Key: JCLOUDS-391
> URL: https://issues.apache.org/jira/browse/JCLOUDS-391
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.6.2
> Environment: Windows 7, Azure and S3
> Reporter: Klaus Müller
> Priority: Critical
>
> Try to set user defined meta data for Azure blob storage. No error setting
> meta data, but when I try to read them, they were not stored for the given
> blob.
> my code (small part of it):
> ...
> BlobStore blobStore = Context.getBlobStore();
> BlobBuilder builder = blobStore.blobBuilder("blob001");
> PayloadBlobBuilder payload = builder.payload(data); // data is
> InputStream
> payload.contentLength(datalen);
> Blob blob = payload.build();
> Map<String, String> keyValueMap = new HashMap<String, String>();
> keyValueMap.put("testmeta","12345");
> blob.getMetadata().setUserMetadata(keyValueMap);
> blobStore.putBlob("container001", blob, multipart() );
> ...
> For S3 it works.
> Is this a known problem with Azure, or something wrong with my code?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
