JDBC
Since Camel 1.2
Only producer is supported
The JDBC component enables you to access databases through JDBC, where SQL queries (SELECT) and operations (INSERT, UPDATE, etc) are sent in the message body. This component uses the standard JDBC API, unlike the SQL Component component, which uses spring-jdbc.
Use the Spring JDBC Component instead of this component, when you use Spring and need to support Spring Transactions. |
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-jdbc</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
This component can only be used to define producer endpoints, which
means that you cannot use the JDBC component in a from()
statement.
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL as a type safe way of configuring endpoints.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The JDBC component supports 4 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
To use the DataSource instance instead of looking up the data source by name from the registry. |
DataSource |
||
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. |
false |
boolean |
|
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 |
boolean |
|
To use a custom strategy for working with connections. Do not use a custom strategy when using the spring-jdbc component because a special Spring ConnectionStrategy is used by default to support Spring Transactions. |
ConnectionStrategy |
Endpoint Options
The JDBC endpoint is configured using URI syntax:
jdbc:dataSourceName
with the following path and query parameters:
Path Parameters (1 parameters)
Name | Description | Default | Type |
---|---|---|---|
Required Name of DataSource to lookup in the Registry. If the name is dataSource or default, then Camel will attempt to lookup a default DataSource from the registry, meaning if there is a only one instance of DataSource found, then this DataSource will be used. |
String |
Query Parameters (14 parameters)
Name | Description | Default | Type |
---|---|---|---|
Whether to allow using named parameters in the queries. |
true |
boolean |
|
Specify the full package and class name to use as conversion when outputType=SelectOne or SelectList. |
String |
||
Determines the output the producer should use. Enum values:
|
SelectList |
JdbcOutputType |
|
Optional parameters to the java.sql.Statement. For example to set maxRows, fetchSize etc. |
Map |
||
The default maximum number of rows that can be read by a polling query. The default value is 0. |
int |
||
Camel will set the autoCommit on the JDBC connection to be false, commit the change after executed the statement and reset the autoCommit flag of the connection at the end, if the resetAutoCommit is true. If the JDBC connection doesn’t support to reset the autoCommit flag, you can set the resetAutoCommit flag to be false, and Camel will not try to reset the autoCommit flag. When used with XA transactions you most likely need to set it to false so that the transaction manager is in charge of committing this tx. |
true |
boolean |
|
Whether transactions are in use. |
false |
boolean |
|
To read BLOB columns as bytes instead of string data. This may be needed for certain databases such as Oracle where you must read BLOB columns as bytes. |
false |
boolean |
|
Set this option to true to use the prepareStatementStrategy with named parameters. This allows to define queries with named placeholders, and use headers with the dynamic values for the query placeholders. |
false |
boolean |
|
Sets whether to use JDBC 4 or JDBC 3.0 or older semantic when retrieving column name. JDBC 4.0 uses columnLabel to get the column name where as JDBC 3.0 uses both columnName or columnLabel. Unfortunately JDBC drivers behave differently so you can use this option to work out issues around your JDBC driver if you get problem using this component This option is default true. |
true |
boolean |
|
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. |
false |
boolean |
|
To use a custom org.apache.camel.component.jdbc.BeanRowMapper when using outputClass. The default implementation will lower case the row names and skip underscores, and dashes. For example CUST_ID is mapped as custId. |
BeanRowMapper |
||
To use a custom strategy for working with connections. Do not use a custom strategy when using the spring-jdbc component because a special Spring ConnectionStrategy is used by default to support Spring Transactions. |
ConnectionStrategy |
||
Allows the plugin to use a custom org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control preparation of the query and prepared statement. |
JdbcPrepareStatementStrategy |
Message Headers
The JDBC component supports 8 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
CamelJdbcUpdateCount (producer) Constant: |
If the query is an UPDATE, query the update count is returned in this OUT header. |
int |
|
Constant: |
If the query is a SELECT, query the row count is returned in this OUT header. |
int |
|
CamelJdbcColumnNames (producer) Constant: |
The column names from the ResultSet as a java.util.Set type. |
Set |
|
CamelJdbcParameters (producer) Constant: |
A java.util.Map which has the headers to be used if useHeadersAsParameters has been enabled. |
Map |
|
CamelRetrieveGeneratedKeys (producer) Constant: |
Set its value to true to retrieve generated keys. |
false |
Boolean |
CamelGeneratedColumns (producer) Constant: |
Set it to specify the expected generated columns. |
String[] or int[] |
|
CamelGeneratedKeysRowCount (producer) Constant: |
The number of rows in the header that contains generated keys. |
int |
|
CamelGeneratedKeysRows (producer) Constant: |
Rows that contains the generated keys. |
List |
Result
By default the result is returned in the OUT body as an
ArrayList<HashMap<String, Object>>
. The List
object contains the
list of rows and the Map
objects contain each row with the String
key as the column name. You can use the option outputType
to control
the result.
Note: This component fetches ResultSetMetaData
to be able to return
the column name as the key in the Map
.
Generated keys
If you insert data using SQL INSERT, then the RDBMS may support auto
generated keys. You can instruct the JDBC producer to
return the generated keys in headers.
To do that set the header CamelRetrieveGeneratedKeys=true
. Then the
generated keys will be provided as headers with the keys listed in the
table above.
Using generated keys does not work with together with named parameters.
Using named parameters
In the given route below, we want to get all the projects from the
projects table. Notice the SQL query has 2 named parameters, :?lic and
:?min.
Camel will then lookup these parameters from the message headers.
Notice in the example above we set two headers with constant value
for the named parameters:
from("direct:projects")
.setHeader("lic", constant("ASF"))
.setHeader("min", constant(123))
.setBody("select * from projects where license = :?lic and id > :?min order by id")
.to("jdbc:myDataSource?useHeadersAsParameters=true")
You can also store the header values in a java.util.Map
and store the
map on the headers with the key CamelJdbcParameters
.
Samples
In the following example, we fetch the rows from the customer table.
First we register our datasource in the Camel registry as testdb
:
Then we configure a route that routes to the JDBC component, so the SQL
will be executed. Note how we refer to the testdb
datasource that was
bound in the previous step:
Or you can create a DataSource
in Spring like this:
With spring xml:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jdbc="http://www.springframework.org/schema/jdbc"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/jdbc
http://www.springframework.org/schema/jdbc/spring-jdbc-3.0.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd">
<!-- PROPERTY PLACEHOLDERS -->
<!--
You may use property placeholders data store configuration
for to do that, you can resolve this properties with srping
-->
<bean id="db" class="org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer">
<property name="location" value="classpath:db.properties"/>
</bean>
<!-- DATA STORE CONFIGURATION -->
<!--
In this example the DataStore is a postgres database, you can change the jdbc connector.
Also, the property testWhileIdle and validationQuery keep connection open.
-->
<bean id="DataStore" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
<property name="driverClassName" value="org.postgresql.Driver" />
<property name="url" value="jdbc:postgresql://${DB_HOST}/${DB_NAME}"/>
<property name="username" value="${DB_USER}" />
<property name="password" value="${DB_PASS}" />
<property name="initialSize" value="4"/>
<property name="maxActive" value="15"/>
<property name="maxIdle" value="16"/>
<property name="minIdle" value="8"/>
<property name="timeBetweenEvictionRunsMillis" value="1800"/>
<property name="minEvictableIdleTimeMillis" value="1800"/>
<property name="testOnBorrow" value="true"/>
<property name="testWhileIdle" value="true"/>
<property name="testOnReturn" value="true"/>
<property name="validationQuery" value="SELECT 1"/>
<property name="maxWait" value="1000"/>
<property name="removeAbandoned" value="true"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="30000"/>
</bean>
<!-- You shuould write a file with an script to initialize your database.
If you have nothing to do with your database, then you can write just a
validation query like 'SELECT *; '-->
<jdbc:initialize-database data-source="DataStore" enabled="true">
<jdbc:script location="classpath:datastore-schema.sql" />
</jdbc:initialize-database>
<camelContext xmlns="http://camel.apache.org/schema/spring">
<!-- CAMEL ROUTE -->
<route id="Reporter">
<from uri="direct:to-datastore"/>
<!-- this example is done with camel-jdbc but you can make it work with camel-sql -->
<setBody>
<simple>insert into test '${body[value]}'</simple>
</setBody>
<to uri="jdbc:DataStore"/>
</route>
</camelContext>
We create an endpoint, add the SQL query to the body of the IN message, and then send the exchange. The result of the query is returned in the OUT body:
If you want to work on the rows one by one instead of the entire ResultSet at once you need to use the Splitter EIP such as:
from("direct:hello")
// here we split the data from the testdb into new messages one by one
// so the mock endpoint will receive a message per row in the table
// the StreamList option allows to stream the result of the query without creating a List of rows
// and notice we also enable streaming mode on the splitter
.to("jdbc:testdb?outputType=StreamList")
.split(body()).streaming()
.to("mock:result");
Sample - Polling the database every minute
If we want to poll a database using the JDBC component, we need to combine it with a polling scheduler such as the Timer or Quartz etc. In the following example, we retrieve data from the database every 60 seconds:
from("timer://foo?period=60000")
.setBody(constant("select * from customer"))
.to("jdbc:testdb")
.to("activemq:queue:customers");
Sample - Move Data Between Data Sources
A common use case is to query for data, process it and move it to another data source (ETL operations). In the following example, we retrieve new customer records from the source table every hour, filter/transform them and move them to a destination table:
from("timer://MoveNewCustomersEveryHour?period=3600000")
.setBody(constant("select * from customer where create_time > (sysdate-1/24)"))
.to("jdbc:testdb")
.split(body())
.process(new MyCustomerProcessor()) //filter/transform results as needed
.setBody(simple("insert into processed_customer values('${body[ID]}','${body[NAME]}')"))
.to("jdbc:testdb");