[ https://issues.apache.org/jira/browse/PHOENIX-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-4058: ---------------------------------- Summary: Generate correct index updates when DeleteColumn processed before Put with same timestamp (was: Generate correct index updates when DeleteColumn processed before Put of same timestamp) > Generate correct index updates when DeleteColumn processed before Put with > same timestamp > ----------------------------------------------------------------------------------------- > > Key: PHOENIX-4058 > URL: https://issues.apache.org/jira/browse/PHOENIX-4058 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > > The following scenario is not handled correctly for mutable secondary > indexing: > 1) indexed column set to null at ts1 (generates a DeleteColumn) > 2) indexed column set to value at ts1 (i.e. different client, same ts) > 3) RS processes (1) first > 4) RS processes (2) next > Because deletes take precedence over puts even though the put happens after > the delete, we still needs to not generate index updates. > The quick fix is to add STORE_NULLS=true to the table as we skirt the issue > since no deletes are issued (i.e. last put wins). -- This message was sent by Atlassian JIRA (v6.4.14#64029)