abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Massyl Nait (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ABDERA-310) s3 acl limitation when creating objects in bucket (no means to specify acl per object)
Date Fri, 09 Nov 2012 12:18:11 GMT

     [ https://issues.apache.org/jira/browse/ABDERA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Massyl Nait updated ABDERA-310:
-------------------------------

    Attachment: camel-aws.patch
    
> s3 acl limitation when creating objects in bucket (no means to specify acl per object)
> --------------------------------------------------------------------------------------
>
>                 Key: ABDERA-310
>                 URL: https://issues.apache.org/jira/browse/ABDERA-310
>             Project: Abdera
>          Issue Type: Improvement
>    Affects Versions: 1.1.2
>         Environment: all
>            Reporter: Massyl Nait
>              Labels: patch
>         Attachments: camel-aws.patch
>
>
> when using s3 component to create new object on amazon bucket, there is no means to specify
acl that will be applied to this newly created object. s3 objects do not inherit acl applied
to the bucket they belong to. 
> in s3 camel component (enpoint) we can specify bucket policy but not objects acl.
> the limitation is in c3producer.
> there is an attachment file (patch) to fix this quickly and whit no impact to existing
code. but i think that we need to enhance the design of this component to be more flexible
and rely on strategy that executes s3 requests that will be to interact wit s3.
> for now there no test for s3producer.
> if we enhance the design we can change or improve this layer with less effort. and we
can do tests obviously.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message