孫驍
11/27/2025, 1:03 PMMAP<STRING, DOUBLE> column.
This keeps one row per business object, but the MAP can contain hundreds of keys.
Option 2 — Use a KV model
Normalize the data into a table shaped like:
id | key | value
This means one row per key, which could expand to hundreds of millions or even billions of rows.
Given this scale and query pattern, which approach is generally better in StarRocks for performance, storage, and analytical efficiency: MAP or KV?
Are there best practices or trade-offs I should consider?
Thanks in advance for any guidance.Murphy
11/28/2025, 2:57 AM