Using Apache Phoenix Secondary Indexes to Speed Up HBase Queries
Learn how to add a Phoenix secondary index to an HBase table, verify that the planner uses it, and weigh the read‑speed gains against write‑amplification and storage costs.
Loading…
ReadMeFeed / Community knowledge
#secondary-index
Real questions. Useful conversations. Find the people who know your stack.
Creating Apache Phoenix Secondary Indexes to Accelerate HBase Queries
Create a Phoenix secondary index on a non‑key column to replace full HBase scans with index scans, cutting query latency. Covers prerequisites, DDL syntax, build monitoring, plan verification, and rollback steps.
Creating and Validating Apache Phoenix Secondary Indexes on HBase Tables
Learn how to create, monitor, and validate a Apache Phoenix secondary index on an HBase table to speed up queries while understanding trade‑offs and recovery steps.
Choosing Between Global and Local Secondary Indexes in Apache Phoenix
Learn how to pick between global and local secondary indexes in Apache Phoenix based on your read/write patterns, with a concrete example showing how to verify index usage via EXPLAIN.
Using Apache Phoenix Secondary Indexes to Speed Up Selective Queries
Learn how to add a global secondary index in Apache Phoenix to turn full table scans into index scans, with a worked example, performance tips, and pitfalls to avoid.
Choosing Between Phoenix Secondary Indexes and Custom Coprocessors for Point‑Read Latency
Guide to choosing between Phoenix secondary indexes and custom coprocessors for lowering point‑read latency in write‑heavy workloads, with a concrete index creation and validation example.
Making Non-Row-Key Queries Fast in Apache Phoenix with Global Secondary Indexes
Phoenix only queries fast on the row key. A global secondary index fixes attribute lookups — here's how it's structured, a worked CREATE INDEX example verified with EXPLAIN, and the write-path costs that decide whether you should use one.
Secondary index scan limitations under strong consistency quorum
Aerospike provides strong consistency for key‑value operations through namespace‑level read and write quorum settings. When these are set to all or majority , the system ensures linearizable reads for direct key accesses by coordinating across replicas. However, secondary index scans do not appear to honor these same namespace‑level quorum configurations. Ev
Phoenix secondary index statistics refresh cadence after bulk data changes
Statistics-Driven Index Selection Phoenix secondary indexes rely on table statistics collected by UPDATE STATISTICS for the optimizer to choose between index access and full scans. After bulk loads, large deletes, or significant data modifications, these statistics become stale and the optimizer may silently revert to suboptimal plans. The system provides no
phoenix