JDBC Processor Config
The JDBC Connector uses different processors which process results in different ways. Some fields will only function with certain processors.
- SQL Query: The SQL Query to run.
- Failed ID: Only works for the Failed ID JDBC Processor (See below)
- ID Field: The field to use as the source repository id
- Fetch Size: Refers to how many rows to fetch from the data source at one time. Default is 10.
- Input Directory: This is for processors where metadata is in the database but the binary content files are on the filesystem. This would be the root directory of the files. You can leave blank if not needed.
- Output Directory: Some processors needs a place to safely store files while doing conversions and processing. This is such a place. You can leave blank if not needed.
- Internal Queue Size: Records to queue before halting read from the data source. Once records fall below the internal queue size, reading will resume.
- Include Content: Check to include content or un-check to exclude content and only retrieve metadata.
- Processor Class: The Processor Class is a registered Spring Bean and is used to process the ResultSet.
Currently, there are two processors included out of the box:
Default JDBC Processor
The default processor runs a query and will convert the table rows into processable documents. It does not use the start and end times configured in the Details tab. In order to filter on date fields, you will need your own WHERE clause.
Failed ID Processor
The Failed ID processor is used for running errors. It is run for each failed document ID and offers the following parameter to insert the id into your failed ids query.
${DOC_ID}
So an example of a failed ID query would be
SELECT * FROM MYTABLE WHERE OBJECTID = '${DOC_ID}'
Output Specification
- JDBC Output Table Name: This field is the name of the table to output items to. Required if not using Auto Create (If not set, and Auto Create is used. The Job Name will be used instead).
- JDBC Output Key: The unique key to find/set/update in the table. Required if not using Auto Create.
- Catalogue: The Catalogue (Or Domain) of the JDBC Instance to connect to. Required if not using Auto Create.
- Schema: The Schema (Or Database/NameSpace) of the JDBC Instance to connect to. Require for Output.
- Binary Column Name: The name of the column where document binaries will be sent to if “Include Binaries” is checked in the job configuration.
- Auto Create: See below
- Quote Identifier: If there are spaces in your table names, catalog names, schema names or column names, enter a quote identifier. For example, SQL Server and Oracle use a double quote “. MySQL uses a backtick `