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

{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.influxdb.CamelInfluxdbSinkConnector",
		"artifactId": "camel-influxdb-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-influxdb-sink",
		"type": "sink",
		"version": "0.7.0",
		"description": "Interact with InfluxDB, a time series database."
	},
	"properties": {
		"camel.sink.path.connectionBean": {
			"name": "camel.sink.path.connectionBean",
			"description": "Connection to the influx database, of class InfluxDB.class",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.batch": {
			"name": "camel.sink.endpoint.batch",
			"description": "Define if this operation is a batch operation or not",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.databaseName": {
			"name": "camel.sink.endpoint.databaseName",
			"description": "The name of the database where the time series will be stored",
			"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.operation": {
			"name": "camel.sink.endpoint.operation",
			"description": "Define if this operation is an insert or a query",
			"defaultValue": "\"insert\"",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.query": {
			"name": "camel.sink.endpoint.query",
			"description": "Define the query in case of operation query",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.retentionPolicy": {
			"name": "camel.sink.endpoint.retentionPolicy",
			"description": "The string that defines the retention policy to the data created by the endpoint",
			"defaultValue": "\"default\"",
			"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.component.influxdb.influxDB": {
			"name": "camel.component.influxdb.influxDB",
			"description": "The shared Influx DB to use for all endpoints",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.influxdb.lazyStartProducer": {
			"name": "camel.component.influxdb.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.influxdb.autowiredEnabled": {
			"name": "camel.component.influxdb.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"
		}
	}
}