ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When a secondary index is defined on a Phoenix table, writes are normally reflected in the index after a short background update. Under a workload of concurrent inserts while an ALTER TABLE ADD COLUMN statement is executing, the index update lag can increase, and the index may temporarily miss some newly added column values. The goal is to understand the exp
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
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