Overview

Topic Adapter Processor is a processor component aimed at labeling records with a dynamic topic, for advanced routing within the pipeline. 

FQCN

com.datumize.ddc.component.adapter.TopicAdapter


It is advisable to group the step that generates output records together with the TopicAdapter in the same thread to save resources and improve efficiency.

Properties


Common properties that apply to all source and processor components of a pipeline.

PROPERTYIDDESCRIPTION

REQUIRED

TYPE

DEFAULT

EXAMPLES

Common
IdentifierIDComponent unique Identifier within the pipeline, read only, only useful for advanced mode.YesStringAuto

MyComponent_23423

This Identifier is automatically generated by the system and you can't change it. Might be helpful for advanced pipeline configuration.

DescriptiondescriptionA short description for the component, to be visualized inside the component representation, aimed at providing additional information to understand the pipeline at a glance.NoString

Extract customer id and loyalty number.

Short and sweet description.

TopictopicAll Source and Processor components support a topic to tag the output records. If the record does not have a tag applied, this topic will be automatically applied. The topic may be used by future components to route, group or classify records.NoString

foo

All output records will be tagged using "foo", unless they have not been tagged during the execution of the step.

PROPERTYIDDESCRIPTIONREQUIREDTYPEDEFAULTEXAMPLES
Default
Topic extractor

extractor

Extractor used to extract a key from the input content. The key will be additionally translated through the mapping, if the mapping is set; if not set, the key will be used as the topic.

Yes

See Extractors section.



Topic mapvalue-topicKey to topic map. This map is optional; if not indicated, the extracted key will be used as the topic.NoMap
keyA=topic1;keyB=topic2
Default topicdefault-topicDefault topic when not matching anything else.NoString

topic1

Last line of defense. If the extracted key is null, or the key can't be mapped then, topic1 will be used as the topic to label the record.