[CAMEL-18366] allow for per-route configuration of streamCaching in YAML

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.18.2, 3.19.0
• Component/s: camel-yaml-dsl
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Bruno Meseguer
• Created: 08/Aug/22 17:03
• Updated: 10/Aug/22 12:46
• Resolved: 10/Aug/22 12:46

Description

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 

camel.main.streamCachingEnabled

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.

Issue Links

• relates to: CAMEL-18374 camel-core - Route template should be able to specify stream-caching option