The RDB via Table connector crawls content from any relational database that can be accessed using JDBC.
Easy Heading Free | ||||
---|---|---|---|---|
|
The RDB via Table connector features include the following:
The content retrieved by the connector is defined entirely using SQL statements, so you can select all or subsets of columns from one or more tables. Initially, the data is inserted into Aspire using the returned column names, but this may be changed by further Aspire processing..
The RDB via Table connects to databases via JDBC, so you'll need the appropriate JDBC client (driver) JAR file for the database you want to connect to. These are available for most (if not all) major database vendors, and your first port of call for the driver should be the vendor's website.
A prerequisite for crawling any RDBMS is to have an RDBMS account. The recommended name for this account is "aspire_crawl_account" or something similar. The username and password for this account will be required below.
The "aspire_crawl_account" will need to have sufficient access rights to read all of the documents in the RDBMS that you wish to crawl.
To set the rights for your "aspire_crawl_account", do the following:
You will need this login information later in these procedures, when entering properties for your RDB Connector via Table.
The Group Expansion connector crawls identities from the identity cache. The Identity Cache is part of Aspire crawl state database. Typically Elastic Search is used as a repository for crawl state database and the Identity Cache is stored in the index aspire-identitycache.
Not relevant here
No special requirements here
Name | Supported |
---|---|
Content Crawling | yes |
Identity Crawling | no |
Snapshot-based Incremental s | yesno |
Non-snapshot-based Incremental s | noyes |
Document Hierarchy | no |
The Group Expansion connector has the following features:
connector can operate in two modes: full and incremental.
Important: The data submitted to Aspire by this connector is dependent entirely on the SQL that's configured. Therefore, it is quite possible to submit all of the data in an incremental crawl, or only some of the data in a full crawl.
In full mode, the connector executes a single SQL database statement and submits each row returned for processing in Aspire.
In incremental mode, there are three stages of processing: preprocessing, crawling, and post-processing.
(Optional) This stage runs a SQL statement against the database that can be used to mark rows to crawl (i.e., they have changed since the previous run).
This stage (similar to full mode) executes a single SQL database statement and submits each row returned for processing in Aspire. Typically, the result set is a subset of the full data that may be filtered using information updated in the (optional) pre-processing stage.
(Optional) Each row of data submitted to Aspire can execute a SQL statement to update its status in the database. This may be to reset a flag set in the (optional) pre-processing stage, thereby denoting the item as processed. Different SQL can be executed for rows that were successfully processed versus ones that were not.
Click here to find out various crawling options
The content retrieved by the connector is defined entirely using SQL statements, so you can select all or subsets of columns from one or more tables. Initially, the data is inserted into Aspire using the returned column names, but this may be changed by further Aspire processing.
The RDB via Tables
The Group Expansion connector is able to crawl the following objects:
Name | Type | Relevant Metadata | Content Fetch & Extraction | Description | ||||
---|---|---|---|---|---|---|---|---|
Seeddatabase row | containertable fields | NA | The identities are grouped by seeds and we crawl identities belonging to seeds | Identity |
| NA | The identities with expanded groupsFields requested by SQL |
No limitations defined