jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Klaus Müller (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-391) can't set user-defined metadata for Azure with multipart blobs
Date Wed, 11 Dec 2013 12:58:07 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845368#comment-13845368
] 

Klaus Müller commented on JCLOUDS-391:
--------------------------------------

Hi Andrew, I did some debug sessions, both with and without multipart. BindAzureBlobMetadataToRequest
 is not called when testing with multipart set. But I did not found the error in source code,
sorry.


> 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.1.4#6159)

Mime
View raw message