node-output-query
Platform reserved (system-utils only). Runs a read-only query against the Core API PostgreSQL database and emits a single JSON artifact listing all matching NodeOutput IDs. There is no pagination in v1: large result sets (for example 170k+ IDs) are returned in one payload for downstream bulk ingest.
When to use it
Use as the discovery step before system-bulk-tabular-writer:
node-output-query → system-bulk-tabular-writerTypical criteria: all outputs from an upload node named csv-input or json-input, optionally scoped by project, session template, simulation name, or session creation window.
Configuration
| Key | Required | Purpose |
|---|---|---|
sourceNodeName | yes | Node instance name to match (for example csv-input). |
sessionTemplateName | no | Case-insensitive match on parent session template name. |
projectId / projectName | no | Scope to one project. |
sessionCreatedFrom / sessionCreatedTo | no | ISO datetimes; filter on session createdAt. |
simulationName | no | Case-insensitive match on Session.SimulationName. |
includeStaticBackedSessions | no | Default false; excludes sessions backing active platform static instances. |
Output shape
{
"sourceNodeName": "csv-input",
"criteria": { "sourceNodeName": "csv-input" },
"totalCount": 172000,
"outputIds": [1, 2, 3]
}The artifact is stored in HEAT Managed Object Store like other system-utils JSON outputs.
Limitations
- Queries core Postgres only; does not connect to optional bulk analytics Postgres.
- Not for trainee-facing dashboards; platform/static bulk ingest pipelines only.
- Very large
outputIdsarrays produce a large JSON blob and long downstream runtime.
Related
- Bulk analytics guide
- system-bulk-tabular-writer
- system-bulk-analytics-query
- bulk-analytics-ingest-reference (shipped preset template name:
bulk-analytics-ingest-reference) - System Utils