Tuple loading topic

Tuple Loading Topics cannot be defined via configuration properties.

TupleTopicDescription Spring Beans are picked up as configuration for the DLC.

Parameter	Required	Type	Default	Description
name	Y	`String`		Name of the topic.
tupleSupplier	Y	`Function<DlcScope, Collection<Object[]>>`		The tuple supplier.
columns		`List<String>`	Columns will implicitly come from the store which is being published to.	The order of columns in the tuples. If a column name matches a datastore column, its parser will be implied. For columns that do not match a datastore column, provide a parser in the channel as a Custom Field. Columns without a matching datastore column or parser are skipped.
channels		`Set<Channel>`	A channel is created using the topic’s name as the name of the target.	Channels
restrictToSources		`Set<String>`		Sources to which the topic is restricted. See source to topic matching.
restrictFromSources		`Set<String>`		Sources from which the topic is restricted. See source to topic matching.

This configuration does not specify a target for the data or the data format.

If the topic is not named the same as the store, the target must be explicitly specified in the channel of the topic.

The target is implicitly the Atoti table named “Trades”.
The format (column order of the tuples and how input fields are parsed) implicitly comes from the columns and types of the targeted Atoti table, in this case “Trades”.

@Bean
public TupleTopicDescription tupleTopic() {
    return TupleTopicDescription.builder("trades", this::generateTuples)
            .build();
}

⌘I