[jira] [Updated] (FLUME-542) S3 sink cannot be used if your AWS keys needs escaping

["Ferenc Szabo (JIRA)" <ji...@apache.org>]

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

Ferenc Szabo updated FLUME-542:
-------------------------------
    Labels: possibly_obsolete  (was: )

> S3 sink cannot be used if your AWS keys needs escaping
> ------------------------------------------------------
>
>                 Key: FLUME-542
>                 URL: https://issues.apache.org/jira/browse/FLUME-542
>             Project: Flume
>          Issue Type: Bug
>          Components: Node
>    Affects Versions: 0.9.3
>         Environment: Amazon EC2 Ubuntu 10.04 LTS
>            Reporter: Disabled imported user
>            Priority: Blocker
>              Labels: possibly_obsolete
>         Attachments: ASF.LICENSE.NOT.GRANTED--FLUME-542.log
>
>
> If you key or secret contains "/" characters, you are instructed to escape them (see http://wiki.apache.org/hadoop/AmazonS3).
> For example:
> {noformat} 
> 19823791823/1232323/nm3nm
> {noformat} 
> ...should be changed to:
> {noformat} 
> 19823791823%2F1232323%2Fnm3nm
> {noformat} 
> When using that in your sink configuration:
> {noformat} 
> collectorSink( "s3n://key:19823791823%2F1232323%2Fnm3nm@str-flume-ec2production/%Y-%m-%d/%H00/", "nginx-" )
> {noformat} 
> ...the Flume collector outputs this:
> {noformat} 
> 2011-02-28 23:06:20,009 WARN com.cloudera.flume.core.Event: Unrecognized escape in event format string: %2
> {noformat} 
> So then we tried double-escaping it:
> {noformat} 
> 19823791823%%2F1232323%%2Fnm3nm
> {noformat} 
> ...which passed the Flume escape check but now fails S3 auth.
> Rob



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)