connectors/camel-nitrite-kafka-connector/src/generated/resources/camel-nitrite-sink.json

{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.nitrite.CamelNitriteSinkConnector",
		"artifactId": "camel-nitrite-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-nitrite-sink",
		"type": "sink",
		"version": "0.7.2",
		"description": "Access Nitrite databases."
	},
	"properties": {
		"camel.sink.path.database": {
			"name": "camel.sink.path.database",
			"description": "Path to database file. Will be created if not exists.",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.collection": {
			"name": "camel.sink.endpoint.collection",
			"description": "Name of Nitrite collection. Cannot be used in combination with repositoryClass option.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.repositoryClass": {
			"name": "camel.sink.endpoint.repositoryClass",
			"description": "Class of Nitrite ObjectRepository. Cannot be used in combination with collection option.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.repositoryName": {
			"name": "camel.sink.endpoint.repositoryName",
			"description": "Optional name of ObjectRepository. Can be only used in combination with repositoryClass, otherwise have no effect",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.lazyStartProducer": {
			"name": "camel.sink.endpoint.lazyStartProducer",
			"description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.synchronous": {
			"name": "camel.sink.endpoint.synchronous",
			"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.password": {
			"name": "camel.sink.endpoint.password",
			"description": "Password for Nitrite database. Required, if option username specified.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.username": {
			"name": "camel.sink.endpoint.username",
			"description": "Username for Nitrite database. Database is not secured if option not specified.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.nitrite.lazyStartProducer": {
			"name": "camel.component.nitrite.lazyStartProducer",
			"description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.nitrite.autowiredEnabled": {
			"name": "camel.component.nitrite.autowiredEnabled",
			"description": "Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.",
			"defaultValue": "true",
			"priority": "MEDIUM",
			"required": "false"
		}
	}
}