[jira] [Work logged] (CAMEL-13734) camel-undertow - Support streaming of large data for HTTP endpoints

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-13734?focusedWorklogId=273091&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-273091 ]

ASF GitHub Bot logged work on CAMEL-13734:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Jul/19 06:43
            Start Date: 08/Jul/19 06:43
    Worklog Time Spent: 10m 
      Work Description: tadayosi commented on pull request #3025: CAMEL-13734: camel-undertow - Support streaming of large data for HTTP endpoints
URL: https://github.com/apache/camel/pull/3025
 
 
   https://issues.apache.org/jira/browse/CAMEL-13734
   
   Split the commits into two parts (consumer and producer) for readability and traceability of changes.
   
   NOTE: In this pull req I reused WebSocket endpoint's `useStreaming` option, promoting it to `common` option.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 273091)
            Time Spent: 10m
    Remaining Estimate: 0h

> camel-undertow - Support streaming of large data for HTTP endpoints
> -------------------------------------------------------------------
>
>                 Key: CAMEL-13734
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13734
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-undertow
>            Reporter: Tadayoshi Sato
>            Assignee: Tadayoshi Sato
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently messages with body of large data {{InputStream}} are always converted to {{byte[]}} on a Camel route for both producer and consumer HTTP endpoints, thus cause {{OutOfMemoryError}} and fail in the middle of processing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)