Property | Required | Description | Default |
---|---|---|---|
locators | yes | A comma separated string of locators that configure which locators to connect to | “localhost[10334]” |
Property | Required | Description | Default |
---|---|---|---|
topicToRegions | yes | A comma separated list of “one topic to many regions” bindings. Each binding is surrounded by brackets. For example “[topicName:regionName], [anotherTopic: regionName, anotherRegion]” | None. This is required to be set in the source connector properties |
nullValuesMeanRemove | no | If set to true, when topics send a SinkRecord with a null value, we will convert to an operation similar to region.remove instead of putting a null value into the region | true |
The topicToRegions property allows us to create mappings between topics and regions. A single one-to-one mapping would look similar to “[topic:region]” A one-to-many mapping can be made by comma separating the regions, for example “[topic:region1,region2]” This is equivalent to both regions being consumers of the topic.
Property | Required | Description | Default |
---|---|---|---|
regionToTopics | yes | A comma separated list of “one region to many topics” mappings. Each mapping is surrounded by brackets. For example "[regionName:topicName], “[anotherRegion: topicName, anotherTopic]” | None. This is required to be set in the source connector properties |
geodeConnectorBatchSize | no | Maximum number of records to return on each poll | 100 |
geodeConnectorQueueSize | no | Maximum number of entries in the connector queue before backing up all Geode cq listeners sharing the task queue | 10000 |
loadEntireRegion | no | Determines if we should queue up all entries that currently exist in the region. This allows us to copy existing region data. Will be replayed whenever a task needs to re-register a cq | true |
durableClientIdPrefix | no | Prefix string for tasks to append to when registering as a durable client. If empty string, will not register as a durable client | "" |
durableClientTimeout | no | How long in milliseconds to persist values in Geode's durable queue before the queue is invalidated | 60000 |
cqPrefix | no | Prefix string to identify Connector cq's on a Geode server | cqForGeodeKafka |
The regionToTopics property allows us to create mappings between regions and topics. A single one-to-one mapping would look similar to “[region:topic]” A one-to-many mapping can be made by comma separating the topics, for example “[region:topic1,topic2]” This is equivalent to the region be a producer for both topics
Possible Upcoming Featured: Formatter - Possibly a JSON to and from PDX formatter Security - security settings for Geode Dynamic Region creation - Dynamically create regions when topics are created (filter what names to look for and what types of regions to create) Allow a single worker to connect to multiple Geode Clusters?