Jira Reader runtime considerations
Metrics monitored by the Jira Reader
The Jira Reader monitors the following metrics.
Metric | Description |
|---|---|
Number of deletes | Number of delete operations |
Number of DDLs | Number of data definition language operations |
Number of PKUpdates | Number of primary key update operations |
Number of updates | Number of update operations |
Number of inserts | Number of insert operations |
Jira Reader limitations
The Jira Reader does not capture DELETE events.
Records for objects that do not support incremental load are synced at every poll, which can create duplicate records. To avoid this, enable Merge mode for the targets of data streams likely to contain records from such objects.
When Striim cannot determine the time of last update for an object, records for that object are duplicated at the target at every poll. The usual cause for this is that the object lacks an
Idfield.If the
IdColumn is of String datatype in some of the tables, a full re-sync will be done at every poll.