On this Page

MetricsHub
MetricsHub Community Connectors 1.0.22

tableUnion (Source)

When To Use

Use tableUnion to append rows from multiple tables into one table.

tableUnion does not perform key matching. It is a row concatenation operation.

Syntax

sources:
  allSensors:
    type: tableUnion
    tables:
    - ${source::monitors.hw.collect.sources.fanSensors}
    - ${source::monitors.hw.collect.sources.psuSensors}

Properties

Property Required Default Description
type Yes None tableUnion.
tables Yes None Ordered list of source tables to concatenate.
computes No [] Post-union processing pipeline.
forceSerialization No false Serialize execution via a per-connector, per-host lock (see the Sources overview). Default false.
  • Ensure all input tables share compatible column layouts.
  • Normalize columns before union (keepColumns, append, prepend, replace).
  • Keep ordering explicit in tables to ease debugging.

Common Mistakes

  • Unioning incompatible schemas and mapping wrong columns.
  • Using union where join semantics are actually required.
  • Forgetting to preserve an origin/type column before union.

Community Examples

tableUnion source merge tables table concatenation metricshub community connector hardware system
Links:
  • [1] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/Redfish/Redfish.yaml
  • [2] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/IpmiTool/IpmiTool.yaml
  • [3] https://github.com/metricshub/community-connectors/blob/main/src/main/connector/hardware/GenericUPS/GenericUPS.yaml
Searching...
No results.