Materialize Documentation
s
Join the Community github/materialize

jsonb_object_agg Function

The jsonb_object_agg(keys, values) aggregate function zips together keys and values into a jsonb object. The input values to the aggregate can be filtered.

Syntax

jsonb_object_agg ( keys , values ORDER BY col_ref ASC DESC , ) FILTER ( WHERE filter_clause )

Signatures

Parameter Type Description
keys any The keys to aggregate.
values any The values to aggregate.

Return value

jsonb_object_agg returns the aggregated key–value pairs as a jsonb object. Each row in the input corresponds to one key–value pair in the output.

If there are duplicate keys in the input, it is unspecified which key–value pair is retained in the output.

If keys is null for any input row, that entry pair will be dropped.

This function always executes on the data from value as if it were sorted in ascending order before the function call. Any specified ordering is ignored. If you need to perform aggregation in a specific order, you must specify ORDER BY within the aggregate function call itself. Otherwise incoming rows are not guaranteed any order.

Usage in dataflows

While jsonb_object_agg is available in Materialize, materializing jsonb_object_agg(expression) is considered an incremental view maintenance anti-pattern. Any change to the data underlying the function call will require the function to be recomputed entirely, discarding the benefits of maintaining incremental updates.

Instead, we recommend that you materialize all components required for the jsonb_object_agg function call and create a non-materialized view using jsonb_object_agg on top of that. That pattern is illustrated in the following statements:

CREATE MATERIALIZED VIEW foo_view AS SELECT * FROM foo;
CREATE VIEW bar AS SELECT jsonb_object_agg(foo_view.bar);

Examples

SELECT jsonb_object_agg(column1, column2) FROM (VALUES ('key1', 1), ('key2', null))
 jsonb_object_agg
------------------
 {"key1": 1, "key2": null}

See also

Did this info help?
Yes No