Custom Properties¶
Use custom properties for settings that the form does not show. The name decides where the setting goes.
| To | Name the property | Example |
|---|---|---|
| Set a platform plugin setting | connector.plugin-config.<setting> | connector.plugin-config.max-connections = 4 caps a Databricks connection pool (default 10). |
| Tune how the connector runs | connector.<setting> | connector.platform-max-connections = 4 |
| Set a property on the connector's own pod (Dedicated only) | any other name | logging.level.com.privacera = DEBUG |
- On a Shared connector, every custom property name must start with
connector.. Global settings for Shared connectors are set in the OmniConnector system application, under System Applications. - A custom property cannot repeat a field that the form already shows.
- Names are case-sensitive, and use only letters, digits,
.,-and_. A name the plugin does not read is silently ignored. - Values are not validated on save. A bad plugin setting fails only that connector. A bad
connector.<setting>value, such as a rate without a unit, can stop the whole pod. On a Shared connector, that is every Shared connector on the Runtime Plane.
Edit and Delete¶
- Shared: every save, create or delete restarts the shared pod. See Deployment mode.
- Dedicated: edits and restarts affect only that connector. Deleting it removes its own application.
- Prev topic: Event Ingestion
- Next topic: Connector Plane UI