{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.reactivestreams.CamelReactivestreamsSinkConnector",
		"artifactId": "camel-reactive-streams-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-reactive-streams-sink",
		"type": "sink",
		"version": "0.12.0-SNAPSHOT",
		"description": "Exchange messages with reactive stream processing libraries compatible with the reactive streams standard."
	},
	"properties": {
		"camel.sink.path.stream": {
			"name": "camel.sink.path.stream",
			"description": "Name of the stream channel used by the endpoint to exchange messages.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.backpressureStrategy": {
			"name": "camel.sink.endpoint.backpressureStrategy",
			"description": "The backpressure strategy to use when pushing events to a slow subscriber. One of: [BUFFER] [OLDEST] [LATEST]",
			"priority": "MEDIUM",
			"required": "false",
			"enum": [
				"BUFFER",
				"OLDEST",
				"LATEST"
			]
		},
		"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.component.reactive-streams.threadPoolMaxSize": {
			"name": "camel.component.reactive-streams.threadPoolMaxSize",
			"description": "The maximum number of threads used by the reactive streams internal engine.",
			"defaultValue": "10",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.reactive-streams.threadPoolMinSize": {
			"name": "camel.component.reactive-streams.threadPoolMinSize",
			"description": "The minimum number of threads used by the reactive streams internal engine.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.reactive-streams.threadPoolName": {
			"name": "camel.component.reactive-streams.threadPoolName",
			"description": "The name of the thread pool used by the reactive streams internal engine.",
			"defaultValue": "\"CamelReactiveStreamsWorker\"",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.reactive-streams.backpressureStrategy": {
			"name": "camel.component.reactive-streams.backpressureStrategy",
			"description": "The backpressure strategy to use when pushing events to a slow subscriber. One of: [BUFFER] [OLDEST] [LATEST]",
			"defaultValue": "\"BUFFER\"",
			"priority": "MEDIUM",
			"required": "false",
			"enum": [
				"BUFFER",
				"OLDEST",
				"LATEST"
			]
		},
		"camel.component.reactive-streams.lazyStartProducer": {
			"name": "camel.component.reactive-streams.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.reactive-streams.autowiredEnabled": {
			"name": "camel.component.reactive-streams.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"
		},
		"camel.component.reactive-streams.reactiveStreamsEngineConfiguration": {
			"name": "camel.component.reactive-streams.reactiveStreamsEngineConfiguration",
			"description": "To use an existing reactive stream engine configuration.",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.reactive-streams.serviceType": {
			"name": "camel.component.reactive-streams.serviceType",
			"description": "Set the type of the underlying reactive streams implementation to use. The implementation is looked up from the registry or using a ServiceLoader, the default implementation is DefaultCamelReactiveStreamsService",
			"priority": "MEDIUM",
			"required": "false"
		}
	}
}