Crates.io | dora-record |
lib.rs | dora-record |
version | 0.3.6 |
source | src |
created_at | 2023-11-01 16:53:23.662614 |
updated_at | 2024-08-28 06:28:30.112413 |
description | `dora` goal is to be a low latency, composable, and distributed data flow. |
homepage | |
repository | https://github.com/dora-rs/dora/ |
max_upload_size | |
id | 1021350 |
size | 75,767 |
dora data recording using Apache Arrow Parquet.
This nodes is still experimental.
cargo install dora-record --locked
- id: dora-record
custom:
source: dora-record
inputs:
image: webcam/image
text: webcam/text
# You can add any input and it is going to be logged.
Format: Parquet file
path: out/<DATAFLOW_ID>/<INPUT>.parquet
Columns:
<INPUT>
: Column containing the input in its defined format.Example:
{
"trace_id": "2fd23ddf1b5d2aa38ddb86ceedb55928",
"span_id": "15aef03e0f052bbf",
"timestamp_uhlc": "7368873278370007008",
"timestamp_utc": 1715699508406,
"random": [1886295351360621740]
}
We can merge input files using the trace_id
that is going to be shared when using opentelemetry features.
trace_id
can also be queried from UI such as jaeger UI, influxDB and so on...trace_id
keep tracks of the logical flow of data, compared to timestamp based merging that might not reflect the actual logical flow of data.