Greetings,

Please excuse any ignorance but my reading of the code indicates that
SinkConnectorConfig should be used for the configuration of sink connectors.

However, there is no mechanism to add additional items to the configuration
as the ConfigDef is created during construction and passed as an argument
to ConnectorConfig where it is "enriched". The enriched version makes a
copy of the original config.  The enriched config is then used to resolve
the key in "Object get(String key)" calls.

What is the proposed mechanism to extend the SinkConnectorConfig?

It almost feels like there should be a ConfigDef builder that is passed
into the constructor so that each derived configuration can adds it's
components before passing on to the root connector config where the
ConfigDef would be built.

As a secondary question.  When developing connectors it is often desirable
to build a sink/source pair to support disaster recovery and other similar
operations where you want to recreate the data.  This means that two
connectors XSink and XSource may need to share common configuration
options; call it XConfig.  Is there a recommended pattern for adding
XConfig options to XSinkConfig and XSourceConfig and ensuring that those
options are added to the base SinkConnectorConfig nad SourceConnectorConfig?

Any guidance is appreciated,
Claude

Reply via email to