data-ingestion

Normalize OHLCV data by configuring provider adapters that convert raw market feeds to UTC-normalized timestamps and consistent dtypes before producing artifacts. Schema validation ensures the standardized data pipeline remains consistent across heterogeneous providers.

Build a deterministic cache for market data ingestion by assigning provider-aware cache keys to OHLCV and trade data. This streamlines data acquisition by preventing redundant fetches and ensuring reliable, deterministic data retrieval across new providers.

The best way to validate market data schema before generating ETL artifacts is to apply schema checks during the normalization process. This verifies that ingested OHLCV feeds align with existing artifacts like ohlcv_series and orderflow_proxy before output.

Add retry logic to market data feeds by implementing provider adapters with explicit retry and backoff mechanisms. This scales data acquisition across multiple providers and ensures consistent OHLCV and trade data pipelines during temporary connection failures.

Data ingestion requires provider adapters with retry logic to integrate new OHLCV feeds. You must configure these adapters alongside cache-aware normalization and validation tests to guarantee data quality and align with existing Candle Compass artifacts.

Inconsistent timestamps in a market data ingestion pipeline occur when raw feeds lack UTC normalization. Applying cache-aware normalization and consistent dtypes during schema validation standardizes timestamps and ensures deterministic data across the system.