ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
Learn how to create, monitor, and maintain Phoenix secondary indexes to speed up non‑primary‑key queries. The post covers index mechanics, a step‑by‑step example, performance trade‑offs, and actionable best practices.
We use Apache Phoenix (5.x) on HBase 2.x and want a documented backup strategy based on HBase snapshots. The goal is a single restore procedure that brings back user tables, their Phoenix secondary indexes, and the SYSTEM.* catalog tables together, so that a restored table is queryable with correct schema and usable indexes. The uncertainty is around consist