ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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.
Learn how to eliminate expensive HBase full table scans using Apache Phoenix secondary indexes to turn O(N) scans into O(log N) point lookups.
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.
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.
The goal is to clarify how Apache Phoenix secondary indexes treat rows where the indexed column contains NULL. Specifically, we need to determine whether such rows are omitted from the index structure or are stored with a special sentinel value that allows the index to be used for queries filtering on NULL. The official documentation does not specify this be