EventTableType
In event-table mode, applications add rows to an event table. On each synchronize cycle, the connector runs a query (specified by the SQL parameter) to extract documents from the table, processes the documents that are returned, and then deletes the rows that it has processed.
This parameter specifies the type of operation to perform on each returned document:
add
- add a new document to the index.update
- update an existing document. This option supports both metadata and content changes. If the content has changed the connector performs an ingest-replace.remove
- delete an existing document.
To perform all of these operations, set up a separate fetch task for each operation.
In the following example, separate tables are used to store the new, modified, and deleted documents. If you use the same table for storing adds, updates, and deletes, ensure that your DeleteEventSql
queries do not delete rows corresponding to other operations/tasks.
[FetchTasks] Number=3 0=EventTableAdd 1=EventTableUpdate 2=EventTableRemove ConnectionString=... [EventTableAdd] EventTableType=add SQL=SELECT id, content FROM event_adds DeleteEventSql=DELETE FROM event_adds WHERE @Clause PrimaryKeys=id Template=document.tmpl [EventTableUpdate] EventTableType=update SQL=SELECT id, content FROM event_updates DeleteEventSql=DELETE FROM event_updates WHERE @Clause PrimaryKeys=id Template=document.tmpl [EventTableRemove] EventTableType=remove SQL=SELECT id FROM event_deletes DeleteEventSql=DELETE FROM event_deletes WHERE @Clause PrimaryKeys=id Template=remove.tmpl
Micro Focus recommends that you use the same template for EventTableType=add
and EventTableType=update
. You can also use the same template with EventTableType=remove
, but this template only needs to include the DREREFERENCE
document field.
Type: | String |
Default: | add |
Required: | No |
Configuration Section: | TaskName or FetchTasks |
Example: | EventTableType=remove
|
See Also: |