You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/02/26 03:45:04 UTC

[jira] [Commented] (JCLOUDS-828) Implement BlobStore UpdateMetadata operations

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

Andrew Gaul commented on JCLOUDS-828:
-------------------------------------

We need to decide whether we want to provide a simpler setMetadata which updates all fields or a more complicated patchMetadata which updates only a subset.  What do the provider APIs allow?

> Implement BlobStore UpdateMetadata operations
> ---------------------------------------------
>
>                 Key: JCLOUDS-828
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-828
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-blobstore
>            Reporter: Timur Alperovich
>
> Multiple blob stores support operations to update the metadata associated with the blob (in S3, this can be done through the PUT-object copy; Swift is already implemented in jclouds; GCS and Azure also use a PUT method). This is preferable to the current approach one has to take with jclouds: get the blob, update metadata, put the blob. If the blob is large, this operation can be prohibitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)