ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to determine whether Apache Phoenix's optional client-side query result cache is automatically invalidated when an HBase region undergoes a split or compaction, so that application developers can decide if manual cache flushing is required to maintain repeatable reads. The cache is keyed by the SQL statement and bound parameters, but Phoenix does
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
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
Goal Determine whether Phoenix 5.x can reduce I/O for low‑traffic scans by pruning column families when statistics are missing. Constraints Sparse, intermittent queries on a large HBase table. Column family cardinality statistics may be stale or absent. Bucket pruning depends on high‑cardinality indexed columns. Uncertainty The optimizer may default to full
When creating a global secondary index in Apache Phoenix, the system registers a PENDING entry in the SYSTEM.CATALOG and initiates a background task to populate data across HBase regions. If a region server hosting a specific partition becomes unavailable during this process, the build task may abort, leaving the index in a FAILED state. This failure state i