You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Dave Hacker (JIRA)" <ji...@apache.org> on 2015/04/17 20:42:59 UTC
[jira] [Created] (PHOENIX-1884) Secondary Indexes which are created
in the middle of a long running upsert have incorrect data
Dave Hacker created PHOENIX-1884:
------------------------------------
Summary: Secondary Indexes which are created in the middle of a long running upsert have incorrect data
Key: PHOENIX-1884
URL: https://issues.apache.org/jira/browse/PHOENIX-1884
Project: Phoenix
Issue Type: Bug
Reporter: Dave Hacker
If an upsert happens at TS1 and ends at TS4 and a secondary index is defined in system.catalog table at TS2 and finishing at TS3 where TS1<TS2<TS3<TS4, then data from the upsert will not be in the index. A one time check at the end of each upsert (i.e. at TS4) needs to be made that determines if there are any new indexes that were not being made at the beginning of the statement and then the data must be upserted into the new indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)