[
https://issues.apache.org/jira/browse/CAMEL-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18366.
---------------------------------
Resolution: Information Provided
You can configure stream-caching per route in yaml-dsl from Camel 3.16 onwards
https://github.com/apache/camel/commit/bed7f5755d3b49b8e83d07af61254ef42be62e1a
> allow for per-route configuration of streamCaching in YAML
> ----------------------------------------------------------
>
> Key: CAMEL-18366
> URL: https://issues.apache.org/jira/browse/CAMEL-18366
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
> Reporter: Bruno Meseguer
> Priority: Major
> Attachments: stage1-gitter-jira.tar.gz
>
>
> Some Web services are designed with HTTP streaming in mind, you invoke them,
> and they maintain the connection open to send back chunks of data at
> different time intervals.
> An example API of such kind is the following:
> [https://developer.gitter.im/docs/streaming-api]
> To define a Source Kamelet that consumes messages from such API, Camel's YAML
> DSL requires the ability to configure the Route option streamCache that is
> enabled by default and requires to be disabled for this use case.
> A workaround to make the Kamelet work is to include the global parameter
> {code:java}
> camel.main.streamCachingEnabled{code}
> Using the workaround however is requiring from the user to include it along
> with its KameletBinding definition, which is not ideal, specially for
> non-Camel users.
> Find attached an example KameletBinding making use of an example Kamelet
> consuming data from the Streaming API above.
> Please note how the global parameter is included. When removing the global
> parameter Camel get's stuck waiting for a full HTTP response that never
> completes because the server maintains the connection open.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
