.jar
file for the JDBC driver on the classpath of the runner. The following is an example of the Java command:
.jar
files.jdbc:mysql://mysql:3306/testdb
jdbc:postgresql://postgres:5432/testdb
jdbc:sqlserver://mssql:1433
jdbc:sqlserver://azure-test.database.windows.net:1433;database=testdbencrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;
jdbc:oracle:thin:@oracledb:1521:orc1
jdbc:db2://db2:50000/testdb
enableAutomaticPagination
to false
.
The batchSize
field sets the number of documents per “page”.
When a SQL query includes pagination terms such as OFFSET
, LIMIT
, or ROWS ONLY
, the SQL query terms override automatic pagination.
When crawling an IBM DB2 database, the pagination method depends on your database version:
--subquery
to the SQL query statement forces the connector to paginate using subqueries regardless of the IBM DB2 database version.${limit}
${offset}
batchSize
.LIMIT
and OFFSET
parameters, respectively.SELECT * FROM example_table LIMIT ${limit} OFFSET ${offset}
SELECT * FROM example_table ORDER BY id OFFSET ${offset} ROWS FETCH NEXT ${limit} ROWS ONLY
SELECT * FROM example_table ORDER BY id OFFSET ${offset} ROWS FETCH NEXT ${limit} ROWS ONLY
${limit}
and ${offset}
pagination variables are the same as in normal crawls.
${last_index_time}
variable for an incremental crawl, which is:
${last_index_time}
property is:
SELECT * FROM example_table WHERE (timestamp_column >= ${last_index_time})
Depending on the database used, it may be necessary to surround ${last_index_time}
in single quotes. For example, '${last_index_time}'
.