BigQuery Nodes
Google BigQuery is the warehouse many plants land their long-term telemetry in. MaestroHub provides one dedicated node for running a SQL query against it within your pipelines.
Configuration Quick Reference
| Field | What you choose | Details |
|---|---|---|
| Parameters | Connection, Function, Function Parameters, Timeout Override | Select the connection profile, function, configure function parameters with expression support, and optionally override timeout. |
| Settings | Description, Timeout (seconds), Retry on Timeout, Retry on Fail, On Error | Node description, maximum execution time, retry behavior on timeout or failure, and error handling strategy. All execution settings default to pipeline-level values. |
BigQuery Query Node
Run a SQL query and deliver its rows. The result is capped at 20,000 rows and about 25 MB by default (the connectors module's queryResultMaxRows / queryResultMaxBytes); a query that returns more is cut short and says so.
| Function Name | Purpose | Common Use Cases |
|---|---|---|
| Query | Execute a SQL query (query) and deliver its rows | KPI reads, backfills, joining plant data with business data |
Output
The Query node delivers its data under result, and execution facts (success, functionId, durationMs, timestamp) under _metadata:
| Expression | Description |
|---|---|
$node["Name"].result.rows | One object per row keyed by column name, up to the result limits (20,000 rows and 25 MB by default). $node["Name"].result.rows[0].<column> reads a value |
$node["Name"].result.rowCount | How many rows were delivered |
$node["Name"]._metadata.truncated | true when a result limit cut the result short — a fact about the call, so it rides with the execution facts |
$node["Name"]._metadata.truncatedBy | Which limit did it — rows (the 20,000-row cap) or bytes (the size budget). Present only when truncated is true |
The job's facts ride along under _metadata next to the four every connected node carries: $node["Name"]._metadata.jobID, _metadata.totalBytesProcessed, _metadata.totalBytesBilled, _metadata.billingTier, _metadata.cacheHit, _metadata.statementType, the job's _metadata.startTime and _metadata.endTime, and _metadata.destinationTable when the job wrote one — plus _metadata.method, _metadata.connectionId and _metadata.protocol.