Available as of Camel 2.16
This component uses
spring-jdbc behind the scenes for the actual SQL handling.
Maven users will need to add the following dependency to their
pom.xml for this component:
This component can be used as a Transactional Client.
The SQL component uses the following endpoint URI notation:
You can append query options to the URI in the following format,
The parameters to the SQL queries are named parameters in the elsql mapping files, and maps to corresponding keys from the Camel message, in the given precedence:
1. Camel 2.16.1: from message body if Simple expression.
java.util.Map3. from message headers
If a named parameter cannot be resolved, then an exception is thrown.
|String||null||Required The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint.|
|null||To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead.|
|Default||To use a vendor specific ElSqlConfig. The possible values are: Default, Postgres, HSql, MySql, Oracle, SqlServer2008, Veritca|
Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to
Reference to a
Sets additional options on the Spring NamedParameterJdbcTemplate that is used behind the scenes to execute the queries. For instance,
Delay in milliseconds between each poll.
Milliseconds before polling starts.
An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set.
Whether to route a single empty Exchange if there was no data to poll.
After processing each row then this query can be executed, if the Exchange was processed successfully, for example to mark the row as processed. The query can have parameter.
After processing each row then this query can be executed, if the Exchange failed, for example to mark the row as failed. The query can have parameter.
After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters.
Make the output of consumer or producer to
Tthe SelectList also supports mapping each row to a Java object as the SelectOne does (only step c).
From Camel 2.18 onwards there is a new StreamList outputType that streams the result of the query using an Iterator. It can be used with the Splitter EIP in streaming mode to process the ResultSet in streaming fashion. This StreamList do not support batch mode, but you can use outputClass to map each row to a class.
Specify the full package and class name to use as conversion when
To store the result as a header instead of the message body. This allows to preserve the existing message body as-is.
If set, will ignore the results of the SQL query and use the existing IN message as the OUT message for the continuation of processing
|Camel 2.16.2: SQL consumer only:Enables or disables transaction. If enabled then if processing an exchange failed then the consumer break out processing any further exchanges to cause a rollback eager|
Result of the query
select operations, the result is an instance of
List<Map<String, Object>> type, as returned by the JdbcTemplate.queryForList() method. For
update operations, the result is the number of updated rows, returned as an
By default, the result is placed in the message body. If the outputHeader parameter is set, the result is placed in the header. This is an alternative to using a full message enrichment pattern to add headers, it provides a concise syntax for querying a sequence or some other small value into a header. It is convenient to use outputHeader and outputType together:
update operations, the SQL Component stores the update count in the following message headers:
The number of rows updated for
The number of rows returned for
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 for these parameters from the message body or message headers. Notice in the example above we set two headers with constant value
for the named parameters:
And the elsql mapping file
Though if the message body is a
java.util.Map then the named parameters will be taken from the body.
In from Camel 2.16.1 onwards you can use Simple expressions as well, which allows to use an OGNL like notation on the message body, where it assumes to have
From Camel 2.18 onwards the producer supports outputType=StreamList that uses an iterator to stream the output of the query. This allows to process the data in a streaming fashion which for example can be used by the Splitter EIP to process each row one at a time, and load data from the database as needed.
And the elsql mapping for allProjects