You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Eric Johnson (JIRA)" <ji...@apache.org> on 2014/12/12 16:21:16 UTC
[jira] [Updated] (LIBCLOUD-612) Google Storage: tags can't be
read/written
[ https://issues.apache.org/jira/browse/LIBCLOUD-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Johnson updated LIBCLOUD-612:
----------------------------------
Assignee: Eric Johnson
Labels: Google (was: )
> Google Storage: tags can't be read/written
> ------------------------------------------
>
> Key: LIBCLOUD-612
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-612
> Project: Libcloud
> Issue Type: Bug
> Components: Storage
> Reporter: Stefan Friesel
> Assignee: Eric Johnson
> Priority: Minor
> Labels: Google
>
> Setting tags via upload_object(..., extra=dict(meta_data={...})) and reading them via get_object('foo').meta_data doesn't work in the Google Storage driver. From what I see in the code this is caused by BaseS3StorageDriver._headers_to_object, which expects the meta data headers to be prefixed with 'x-amz-meta-'. I checked the libcloud debug output and on Google Storage they are prefixed with 'x-goog-meta-'.
> Should the Google driver override the method (although it's private) or should BaseS3StorageDriver._headers_to_object accept both prefixes? Or something else? Depending on what the preferred solution is, I would make a pullrequest for this.
> Is there ongoing work to have a Google Storage Driver using the native Google API?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)