camel-wordpress-kafka-connector source configuration
Connector Description: Manage posts and users using Wordpress API.
When using camel-wordpress-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-wordpress-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this source connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.wordpress.CamelWordpressSourceConnector
The camel-wordpress source connector supports 24 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required The endpoint operation. One of: [post] [user]. Enum values:
|
HIGH |
||
The second part of an endpoint operation. Needed only when endpoint semantic is not enough, like wordpress:post:delete One of: [delete]. Enum values:
|
MEDIUM |
||
The Wordpress REST API version. |
"2" |
MEDIUM |
|
The criteria to use with complex searches. |
MEDIUM |
||
Whether to bypass trash and force deletion. |
false |
MEDIUM |
|
The entity ID. Should be passed when the operation performed requires a specific entity, e.g. deleting a post. |
MEDIUM |
||
Password from authorized user. |
MEDIUM |
||
Search criteria. |
MEDIUM |
||
Required The Wordpress API URL from your site, e.g. http://myblog.com/wp-json/. |
HIGH |
||
Authorized user to perform writing operations. |
MEDIUM |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
MEDIUM |
|
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
MEDIUM |
||
Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]. Enum values:
|
MEDIUM |
||
The Wordpress REST API version. |
"2" |
MEDIUM |
|
Wordpress configuration. |
MEDIUM |
||
The criteria to use with complex searches. |
MEDIUM |
||
Whether to bypass trash and force deletion. |
false |
MEDIUM |
|
The entity ID. Should be passed when the operation performed requires a specific entity, e.g. deleting a post. |
MEDIUM |
||
Password from authorized user. |
MEDIUM |
||
Search criteria. |
MEDIUM |
||
Required The Wordpress API URL from your site, e.g. http://myblog.com/wp-json/. |
HIGH |
||
Authorized user to perform writing operations. |
MEDIUM |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
MEDIUM |
|
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. |
true |
MEDIUM |
The camel-wordpress source connector has no converters out of the box.
The camel-wordpress source connector has no transforms out of the box.
The camel-wordpress source connector has no aggregation strategies out of the box.