You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Brendan Long (JIRA)" <ji...@apache.org> on 2011/06/20 21:56:47 UTC
[jira] [Created] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
------------------------------------------------------------------------
Key: CAMEL-4126
URL: https://issues.apache.org/jira/browse/CAMEL-4126
Project: Camel
Issue Type: Improvement
Components: camel-atom
Affects Versions: 2.8.0
Reporter: Brendan Long
Priority: Minor
With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
Not including the content type means S3 will be serving the uploaded file as generic binary.
Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller closed CAMEL-4126.
-----------------------------------
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Brendan Long (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brendan Long updated CAMEL-4126:
--------------------------------
Component/s: (was: camel-atom)
camel-aws
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Priority: Minor
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Brendan Long (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brendan Long updated CAMEL-4126:
--------------------------------
Attachment: s3-content-length-and-type-patch.diff
Patch to use these headers
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Priority: Minor
> Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller reassigned CAMEL-4126:
---------------------------------------
Assignee: Christian Müller
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Assignee: Christian Müller
> Priority: Minor
> Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller resolved CAMEL-4126.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Richard Kettelerij (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052193#comment-13052193 ]
Richard Kettelerij commented on CAMEL-4126:
-------------------------------------------
Patches are always welcome.
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Priority: Minor
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4126) S3Producer does not use
CamelAwsS3ContentLength or CamelAwsS3ContentType
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055176#comment-13055176 ]
Christian Müller commented on CAMEL-4126:
-----------------------------------------
Committed r1139939
Thanks Brendan for the patch.
Working on the wiki page...
> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
> Key: CAMEL-4126
> URL: https://issues.apache.org/jira/browse/CAMEL-4126
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.8.0
> Reporter: Brendan Long
> Assignee: Christian Müller
> Priority: Minor
> Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN AmazonS3Client - No content length specified for stream data. Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira