libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Friesel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-612) Google Storage: tags can't be read/written
Date Tue, 09 Sep 2014 17:12:29 GMT

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

Stefan Friesel commented on LIBCLOUD-612:
-----------------------------------------

I opened a PR (https://github.com/apache/libcloud/pull/356) with a alternative solution using
a custom header prefix as I noticed Google also replaced "X-AMZ-Storage-Class:" with "X-Goog-Storage-Class:",
same for ACL (https://developers.google.com/storage/docs/reference-methods).

> 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
>            Priority: Minor
>
> 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)

Mime
View raw message