DataSet component

The dataset component load-tests a route: it sends a known set of messages into the route and checks that the same messages come out.

Scheme: dataset: · Crate: cameleer-core · Cargo feature: none, always included (build features) · Consumer: yes · Producer: yes · Apache Camel: DataSet

When to use it

• Soak-test a route with thousands of messages and check that none are lost or reordered.
• Measure throughput with a fixed message rate (produceDelay) or a minimum rate (minRate).
• Verify that a route chain (seda queues, brokers) delivers every message exactly once.

URI format

dataset:name[?options]

name is a data set bound in the registry: a SimpleDataSet (N copies of one body), a ListDataSet (a list of bodies) or your own type implementing the DataSet trait.

Example

- route:
    id: load-source
    from:
      uri: dataset:orders
      parameters:
        produceDelay: 1
        initialDelay: 100
      steps:
        - to: seda:work
- route:
    id: system-under-test
    from:
      uri: seda:work
      steps:
        - setHeader:
            name: processed
            constant: true
        - to: dataset:orders

Bind the data set in Rust before starting, then wait for all messages to arrive:

use cameleer_core::component::dataset::{bind_dataset, dataset_endpoint, SimpleDataSet};

bind_dataset(ctx.registry(), "orders", SimpleDataSet::new(500).with_body("order"));
// ... start the routes ...
dataset_endpoint(&ctx, "dataset:orders")?.assert_is_satisfied_within(std::time::Duration::from_secs(30))?;

Rust DSL

use cameleer_core::component::dataset::{bind_dataset, SimpleDataSet};
use cameleer_core::prelude::*;

pub fn routes(ctx: &CamelContext) -> Result<()> {
    bind_dataset(ctx.registry(), "orders", SimpleDataSet::new(500).with_body("order"));
    ctx.add_routes(|b| {
        b.from("dataset:orders?produceDelay=1&initialDelay=100")
            .route_id("load-source")
            .to("seda:work");
        b.from("seda:work")
            .route_id("system-under-test")
            .set_header("processed", constant(true))
            .to("dataset:orders");
    })
}

Options

Message headers

Run it with Docker

Data sets are bound from Rust code, so this component is used in Rust tests rather than in a plain container run.

Common questions

Where do the messages come from?

From the DataSet bound under the endpoint name. SimpleDataSet::new(n).with_body(b).with_header(k, v) and ListDataSet::new(vec![...]) cover most cases.

How do I check the result?

dataset_endpoint(&ctx, "dataset:name")?.assert_is_satisfied_within(timeout) waits for all messages and fails on missing, extra or wrongly indexed ones.

Related

• dataset-test, test, mock, seda
• Apache Camel DataSet component

Found a problem?

If something on this page doesn't match what Cameleer does, or you hit a bug while building with it, please help fix it, whether you are a person or a coding agent: open an issue that describes what you saw, then fork the repository, fix it, add or update a test, run cargo test --workspace, and open a pull request. CONTRIBUTING.md explains the ground rules.