marpledata 3.3.0__tar.gz → 3.4.0.dev1__tar.gz

marpledata-3.4.0.dev1/.env.local

@@ -0,0 +1,3 @@
+MDB_URL=http://localhost:8000/api/v1
+MDB_TOKEN=mdb_9iSQvvT6r75iUhIksAyut_0jrWsRryR_unc6vrWviwU
+

marpledata-3.4.0.dev1/.env.nightly

@@ -0,0 +1,2 @@
+MDB_URL=https://db.nightly.marpledata.com/api/v1
+MDB_TOKEN=mdb_2FFW5oalKPBnK_7aejBzkZO-FGxHHIIpInlwYkOMypM

marpledata-3.4.0.dev1/.env.staging

@@ -0,0 +1,4 @@
+MDB_TOKEN=mdb_BfGpBUolaa4OlZpl-npTdq497-fVlXrCIRSUEVgox7Y
+MDB_URL=https://db.staging.marpledata.com/api/v1
+INSIGHT_TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJodHRwczovL2FwcC5nZXRtYXJwbGUuaW8vYXBpLyIsImlzcyI6Imh0dHBzOi8vZGV2LXY4OHh3a213LmV1LmF1dGgwLmNvbS8iLCJpYXQiOjE3NzQ4NzI2MDMuNDk5NDc5OCwiZXhwIjoxNzc3NDY0NTkwLjgyNywic3ViIjoiZmMyZGQ1NmUtM2NiMC00YjEzLWIwYjMtMDFmYjZmNjk1MzNmIiwiaHR0cHM6Ly9tYXJwbGVkYXRhLmNvbS9lbWFpbF92ZXJpZmllZCI6dHJ1ZSwiaHR0cHM6Ly9tYXJwbGVkYXRhLmNvbS9hcGlfdG9rZW4iOiJiNDAzYWNlZi0xOWI0LTQ1MTMtYmJmMy0wN2Q2MzQ1MTY1ZTQifQ.-LxExjnpxFD_xGZE6xdX20GHalXMWRBSN02Bjt9lx00
+INSIGHT_URL=https://insight.staging.marpledata.com/api/v1

{marpledata-3.3.0 → marpledata-3.4.0.dev1}/CHANGELOG.md

@@ -5,6 +5,16 @@ All notable changes to the Python SDK package `marpledata` will be documented in
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.4.0] - 2026-07-16
+
+### Added
+
+- `Dataset.add_signal` and `Dataset.add_signals` to upload signal data onto an existing dataset (presign → write → PUT → complete). Accepts DataFrame, Arrow table, or on-disk parquet matching `LAKE_ARROW_SCHEMA` (`time` plus `value` and/or `value_text`); supports concurrent uploads, batch-level `overwrite`, import `priority`, and automatic ~1M-row groups / ~16M-row file splits.
+- `Signal.wait_until_available` to poll until a signal is queryable (storage status is no longer `FROZEN_TO_COLD`; typical after `add_signal`).
+- `SignalUpload` input model and `SignalsAlreadyExistError` for HTTP 409 presign conflicts (duplicate / already exists).
+- Exported `LAKE_ARROW_SCHEMA` describing the input columns for signal upload (alongside existing realtime `SCHEMA` for `Dataset.append`).
+- `Dataset.get_signals(signal_ids=...)` to fetch signals by ID (order preserved), plus `refresh` on `get_signal` / `get_signals` to bypass the local cache.
+
 ## [3.3.0] - 2026-06-29
 
 ### Added

{marpledata-3.3.0 → marpledata-3.4.0.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: marpledata
-Version: 3.3.0
+Version: 3.4.0.dev1
 Summary: Marple SDK for Python
 Project-URL: Homepage, https://www.marpledata.com/
 Project-URL: Documentation, https://marpledata.gitlab.io/marple-sdk/
@@ -87,6 +87,37 @@ dataset = stream.push_file("examples_race.csv", metadata={"driver": "Mbaerto"})
 dataset = dataset.wait_for_import(timeout=10)
 ```
 
+#### Add signals to an imported dataset
+
+Upload additional signals (for example derived channels) on an existing dataset.
+Each signal is a DataFrame, Arrow table, or on-disk parquet matching `LAKE_ARROW_SCHEMA`:
+columns `time` (int64 nanoseconds) plus `value` and/or `value_text`.
+Times must overlap the dataset time range. Use `overwrite=True` to replace an existing signal name;
+a conflict without overwrite raises `SignalsAlreadyExistError`.
+
+```python
+import pandas as pd
+from marple.db import LAKE_ARROW_SCHEMA  # time + value and/or value_text
+
+speed = dataset.get_signal("car.speed").get_data()
+derived = pd.DataFrame({
+    "time": speed.index.asi8,
+    "value": speed["value"] * 3.6,
+})
+# Single signal: wait until available before reading
+signal = dataset.add_signal(
+    "car.speed_kmh",
+    derived,
+    metadata={"unit": "km/h"},
+).wait_until_available()
+
+# Batch: returns IDs as soon as upload completes (no wait)
+ids = dataset.add_signals([
+    {"name": "car.speed_kmh", "data": derived, "metadata": {"unit": "km/h"}},
+], overwrite=True, concurrency=4)
+signals = dataset.get_signals(signal_ids=ids)
+```
+
 #### Upload large files
 
 `stream.push_file(...)` starts an ingestion and lets the Marple DB API choose the best upload mode. Depending on the deployment and file size, the SDK can upload through the API server, upload directly to Azure Blob Storage, use a single presigned URL, or split the file into multipart uploads.
@@ -173,6 +204,9 @@ if len(datasets) > 0:
 - **List streams**: `db.get_streams()`
 - **List datasets in a stream**: `stream.get_datasets()`
 - **Upload a file to a file-stream**: `stream.push_file(file_path, metadata={...}, concurrency=4)`
+- **Add signals to a dataset**: `dataset.add_signal(name, data, ...)` / `dataset.add_signals([...])` — data matches `LAKE_ARROW_SCHEMA` (`time` + `value` and/or `value_text`)
+- **Wait until a signal is available**: `signal.wait_until_available(timeout=60)`
+- **Fetch signals by ID**: `dataset.get_signals(signal_ids=[...], refresh=False)`
 - **Wait for a dataset to import**: `dataset.wait_for_import(timeout=60)`
 - **Download original uploaded file**: `dataset.download(destination_folder=".")`
 - **Download parquet for a signal**: `dataset.get_signal(signal_name).download(destination_folder=".")`

{marpledata-3.3.0 → marpledata-3.4.0.dev1}/README.md

@@ -52,6 +52,37 @@ dataset = stream.push_file("examples_race.csv", metadata={"driver": "Mbaerto"})
 dataset = dataset.wait_for_import(timeout=10)
 ```
 
+#### Add signals to an imported dataset
+
+Upload additional signals (for example derived channels) on an existing dataset.
+Each signal is a DataFrame, Arrow table, or on-disk parquet matching `LAKE_ARROW_SCHEMA`:
+columns `time` (int64 nanoseconds) plus `value` and/or `value_text`.
+Times must overlap the dataset time range. Use `overwrite=True` to replace an existing signal name;
+a conflict without overwrite raises `SignalsAlreadyExistError`.
+
+```python
+import pandas as pd
+from marple.db import LAKE_ARROW_SCHEMA  # time + value and/or value_text
+
+speed = dataset.get_signal("car.speed").get_data()
+derived = pd.DataFrame({
+    "time": speed.index.asi8,
+    "value": speed["value"] * 3.6,
+})
+# Single signal: wait until available before reading
+signal = dataset.add_signal(
+    "car.speed_kmh",
+    derived,
+    metadata={"unit": "km/h"},
+).wait_until_available()
+
+# Batch: returns IDs as soon as upload completes (no wait)
+ids = dataset.add_signals([
+    {"name": "car.speed_kmh", "data": derived, "metadata": {"unit": "km/h"}},
+], overwrite=True, concurrency=4)
+signals = dataset.get_signals(signal_ids=ids)
+```
+
 #### Upload large files
 
 `stream.push_file(...)` starts an ingestion and lets the Marple DB API choose the best upload mode. Depending on the deployment and file size, the SDK can upload through the API server, upload directly to Azure Blob Storage, use a single presigned URL, or split the file into multipart uploads.
@@ -138,6 +169,9 @@ if len(datasets) > 0:
 - **List streams**: `db.get_streams()`
 - **List datasets in a stream**: `stream.get_datasets()`
 - **Upload a file to a file-stream**: `stream.push_file(file_path, metadata={...}, concurrency=4)`
+- **Add signals to a dataset**: `dataset.add_signal(name, data, ...)` / `dataset.add_signals([...])` — data matches `LAKE_ARROW_SCHEMA` (`time` + `value` and/or `value_text`)
+- **Wait until a signal is available**: `signal.wait_until_available(timeout=60)`
+- **Fetch signals by ID**: `dataset.get_signals(signal_ids=[...], refresh=False)`
 - **Wait for a dataset to import**: `dataset.wait_for_import(timeout=60)`
 - **Download original uploaded file**: `dataset.download(destination_folder=".")`
 - **Download parquet for a signal**: `dataset.get_signal(signal_name).download(destination_folder=".")`