public class SampleScenarios extends Object
TOPICS
BOOTSTRAP_SERVERS and TOPICS if required
SampleScenarios SampleScenarios.Scenario as Java application (eg. SampleScenarios KAFKA_SINK)
with all dependent jars in the CLASSPATH (eg. from IDE).
| Modifier and Type | Class and Description |
|---|---|
static class |
SampleScenarios.AtmostOnce
This sample demonstrates a flow with at-most once delivery.
|
static class |
SampleScenarios.FanOut
This sample demonstrates a flow where messages are consumed from a Kafka topic and processed
by multiple streams with each transformed stream of messages stored in a separate Kafka topic.
|
static class |
SampleScenarios.KafkaExactlyOnce
This sample demonstrates an exactly/once transactional flow where messages are received
from partitions of a source topic, transformed and sent to a destination topic using a
transactional sender.
|
static class |
SampleScenarios.KafkaSink
This sample demonstrates the use of Kafka as a sink when messages are transferred from
an external source to a Kafka topic.
|
static class |
SampleScenarios.KafkaSinkChain
This sample demonstrates the use of Kafka as a sink when messages are transferred from
an external source to a Kafka topic.
|
static class |
SampleScenarios.KafkaSource
This sample demonstrates the use of Kafka as a source when messages are transferred from
a Kafka topic to an external sink.
|
static class |
SampleScenarios.KafkaTransform
This sample demonstrates a flow where messages are consumed from a Kafka topic, transformed
and the results stored in another Kafka topic.
|
static class |
SampleScenarios.PartitionProcessor
This sample demonstrates a flow where messages are consumed from a Kafka topic, processed
by multiple threads and the results stored in another Kafka topic.
|
static class |
SampleScenarios.Person |
static class |
SampleScenarios.PersonSerDes |
protected static class |
SampleScenarios.Scenario |
static class |
SampleScenarios.TransactionalSend
This sample demonstrates the use of transactions to send data to multiple topic partitions,
such that if one of the sends fails, the transaction is aborted and the data from uncommitted
transactions are not visible to consumers configured with
ConsumerConfig.ISOLATION_LEVEL_CONFIG
read_committed. |
| Constructor and Description |
|---|
SampleScenarios() |