Hybrid Configurable Feed
caution
Supported only in TimeBase 4.3
Hybrid process is used to merge historical and live data. Aggregator downloads historical data from Feed provider on process start and then subscribes for live data feed.
- Edit Aggregator Processes: right-click the Aggregator box and select Edit Processes.
- New Configurable Feed Process: Select New... drop-down menu and select New Hybrid Configurable Feed. This will launch the Data Connector Wizard that is used to define a configurable feed process.
- Refer to Configure General Process Properties section for settings.
- Specific settings for Hybrid Configurable Feed:
| Property | Description |
|---|---|
| New Instrument Backfill Depth | Backfill depth for new instruments. Applied only to instruments, which have not loaded data yet. |
| Max backfill depth | Maximum backfill depth. Applied unconditionally. It causes a gap in data, when lastMsgTimestamp < now - maxBackfillDepth for a given symbol. Use the parameter only when gaps are ok for your scenario. |
| Live Message Buffer Size | Number of live data messages (per instrument) that will be buffered while Aggregator restores history. |
| Min Historical Depth | Minimum time range for historical query. |
| Max Duration | Maximum process duration. If specified, the process will be terminated after reaching this limit. |
| Max History Data Lag | Maximum time historical feed may possibly lag behind live data. If historical feed has not returned any data for T > "Max History Data Lag", the aggregator can then safely assume that there was no live data between (now - T) and (now - "Max History Data Lag"). |
| Switch to Live is no History | Switch to Live feed, when history cannot be loaded longer than "Max History Data Lag. |
| Max Live Data Lag | Maximum time live feed may possibly lag behind live data. If live feed has not returned any data for T > "Max Live Data Lag", the aggregator can then safely assume that there was no live data between (now - T) and (now - "Max Live Data Lag"). |
| Max Sequential Catch-Up Attempts | Maximum number of attempts to catch up with live data, after which aggregator temporarily gives up and pushes the symbol to the back of the catch up queue. |
| Historical Thread Count | Number of worker threads responsible for history restoration. |
- Proceed through the Data Connector Wizard and complete the process configuration.
- After hybrid process start, history and then live data will be loaded into the target stream.