Phoenix Secondary Indexes vs Row-Key Range Scans
Choose between Phoenix secondary indexes and row-key range scans, then validate with EXPLAIN before and after index creation.
Loading…
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Choose between Phoenix secondary indexes and row-key range scans, then validate with EXPLAIN before and after index creation.
Speed up non-row-key lookups in Apache Phoenix with secondary indexes, but verify planner selection with EXPLAIN and account for write amplification.
Decide whether a Phoenix materialized view fits your HBase aggregation workload, with option trade-offs, sample DDL, and validation checks.
Filtering a Phoenix table by a non‑key column forces a full table scan. Adding a secondary index turns that scan into an index lookup, cutting read latency while adding modest write overhead.
Compare Global and Local secondary indexes in Apache Phoenix to balance write throughput and read latency in HBase-backed applications.
Phoenix secondary indexes are separate HBase tables, not magic. Learn when a global index is worth the synchronous write cost, when a local index fits your access pattern, and how covering columns trade storage for read speed.
Implement a lightweight, low‑latency aggregation layer with Phoenix materialized views. This guide walks through the minimal design, trust boundaries, operational checks, and failure modes to help you decide if MV is right for your use case.
Architecture note on adding a single‑column Phoenix secondary index: requirements, minimal design, consistency boundaries, operational checks, failure modes, and when to revisit the design.
Phoenix has no CREATE MATERIALIZED VIEW statement — the supported equivalent is a view with a covering index. Here's how the mechanism works, a worked example, and the pitfalls.