feat(platform): add managed data product history plane
This commit is contained in:
@@ -9,8 +9,8 @@ qualified:
|
||||
|
||||
- `n8n-nodes-ndc.ndcDataProductPublish` — publishes canonical facts into an
|
||||
approved Data Product.
|
||||
- `n8n-nodes-ndc.ndcDataProductRead` — reads the current snapshot of an
|
||||
approved Data Product.
|
||||
- `n8n-nodes-ndc.ndcDataProductRead` — reads the current snapshot or a bounded,
|
||||
cursor-paged history window of an approved Data Product.
|
||||
- `n8n-nodes-ndc.ndcFoundryBinding` — creates or updates a declarative Foundry
|
||||
page-slot binding. This is a control-plane operation, not a runtime data
|
||||
transport.
|
||||
@@ -42,6 +42,7 @@ never accepts them from a workflow.
|
||||
- `GET /internal/data-plane/v1/reader/data-products`
|
||||
- `POST /internal/data-plane/v1/data-products/:dataProductId/publish`
|
||||
- `GET /internal/data-plane/v1/data-products/:dataProductId/snapshot`
|
||||
- `GET /internal/data-plane/v1/data-products/:dataProductId/history`
|
||||
- `GET /internal/foundry/v1/data-products`
|
||||
- `POST /internal/foundry/v1/data-product-bindings`
|
||||
|
||||
@@ -58,14 +59,20 @@ materializes actor, owner and exact application/page/binding/product scope from
|
||||
that grant; none of those authorization claims are accepted from headers or
|
||||
workflow data.
|
||||
|
||||
`NDC Data Product Read` supports only the bounded
|
||||
`nodedc.data-product.snapshot/v1` contract. Its `Page Size` parameter is a
|
||||
`NDC Data Product Read` supports the bounded
|
||||
`nodedc.data-product.snapshot/v1` contract. Its snapshot `Page Size` parameter is a
|
||||
safety ceiling, not pagination: the complete scoped current projection must fit
|
||||
within 5000 entity keys. A larger product returns
|
||||
`data_product_snapshot_limit_exceeded`; the node must not assemble independent
|
||||
pages or start a patch stream from an incomplete snapshot. Large products need
|
||||
stable partition Data Products or a separately versioned query contract with a
|
||||
single snapshot barrier.
|
||||
stable partition Data Products.
|
||||
|
||||
History mode uses `nodedc.data-product.history/v1` and requires a closed
|
||||
`from`/`to` interval. It supports provider-neutral `sourceIds`, a resolution
|
||||
that is a multiple of the Data Product native sampling interval, a limit up to
|
||||
5000 points and an opaque keyset continuation cursor. The response stays as one
|
||||
envelope item so L2 logic can preserve `query` and `nextCursor` while iterating.
|
||||
The workflow never selects a database, provider, tenant or connection.
|
||||
|
||||
## Publish input
|
||||
|
||||
|
||||
Reference in New Issue
Block a user