From 832551a8a9e3f043d121f5a5d5aa83007cfdbfca Mon Sep 17 00:00:00 2001 From: Gianluca Date: Mon, 11 Mar 2024 15:12:43 +0100 Subject: [PATCH] Checkpoint --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index d302ee22..81b74afd 100644 --- a/README.md +++ b/README.md @@ -53,8 +53,8 @@ - [`record.extraction.error.strategy`](#recordextractionerrorstrategy) - [Topic Mapping](#topic-mapping) - [Record Routing (`map..to`)](#record-routing-maptopicto) - - [Record Mapping (`fields.`)](#record-mapping-fieldsfiledname) - - [Filtered Record Routing](#filtered-record-routing) + - [Record Mapping (`field.`)](#record-mapping-fieldfiledname) + - [Filtered Record Routing (`item-template.`)](#filtered-record-routing-item-templatetemplate-name) - [Example](#example) - [Schema Registry](#schema-registry) - [`schema.registry.url`](#schemaregistryurl) @@ -907,7 +907,7 @@ This configuration enables the implementation of various mapping scenarios, as s With this scenario, it is possible to broadcast to all clients subscribed to a single item (`sample-item`) every message published to different topics (`sample-topic1`, `sample-topic2`, `sample-topic3`). -##### Record Mapping (`fields.`) +##### Record Mapping (`field.`) To forward real-time updates to the Lightstreamer clients, a Kafka record must be mapped to Lightstreamer fields, which define the _schema_ of any Lightstreamer item. @@ -995,7 +995,7 @@ The `QuickStart` [factory configuration file](kafka-connector/src/connector/dist #{VALUE.item_status} ``` -##### Filtered Record Routing +##### Filtered Record Routing (`item-template.`) Besides mapping topics to statically predefined items, Kakfa Connector allows to define _item templates_, which enable to filter the routing of Kafka records by matching the contents against a _parameterized_ subscribed item.