Support Questions
Find answers, ask questions, and share your expertise
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Null fields when using Phoenix index


Null fields when using Phoenix index


I have a table in Phoenix used for ETL auditing. This table has a composite key of three columns. I have recently add a secondary index on a fourth column to speed up queries on this column. However I have noticed an odd behaviour: on all rows that were in the table before the index was created, columns other than the key columns and the index are <null>. For all rows inserted into the table after the creation of the index, all columns are populated. Since this is a write heavy table (~500 000 rows inserted per day), I have used a local index. I have two questions:

1) Is this expected behaviour for a Phoenix index, or does it indicate an error on my part?

2) How can I cause the <null> fields to be populated? I am willing to recreate the index if necessary

Don't have an account?
Coming from Hortonworks? Activate your account here