Expand description
§wf-connector-api
Minimal Arrow-native connector API for warp-fusion.
§Design
wp-connector-api sources produce SourceEvent { payload: RawData },
designed for downstream parse pipelines. CEP engines like warp-fusion
operate on Arrow RecordBatch directly.
wf-connector-api fills this gap — one trait for sources, extensible
to sinks in the future (e.g. BatchSink for Arrow-native output).
§Relationship with wp-connector-api
| wp-connector-api | wf-connector-api | |
|---|---|---|
| Source data | SourceEvent { payload: RawData } | RecordBatch (columnar) |
| Consumer | parse pipeline (WPL) | CEP engine (warp-fusion) |
| Error model | SourceResult<T> (orion-error) | SourceResult<T> (orion-error) |
| Lifecycle | start() / receive() / close() | start() / receive_batch() / close() |
wp-connectors (the implementation crate) can implement BOTH traits
for the same connector (Kafka / File / TCP), sharing connection logic.
Enums§
- Source
Reason - Connector error reason.
Traits§
- Batch
Source - A batch-oriented data source that produces Arrow
RecordBatches.