You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/12/02 03:09:10 UTC
[jira] [Created] (PHOENIX-2478) Rows committed in transaction
overlapping index creation are not populated
James Taylor created PHOENIX-2478:
-------------------------------------
Summary: Rows committed in transaction overlapping index creation are not populated
Key: PHOENIX-2478
URL: https://issues.apache.org/jira/browse/PHOENIX-2478
Project: Phoenix
Issue Type: Bug
Reporter: James Taylor
For a reproducible case, see IndexIT.testCreateIndexAfterUpsertStarted() and the associated FIXME comments for PHOENIX-2446.
The case that is failing is when a commit starts before an index exists, but commits after the index build is completed. For transactional data, this is problematic because the index gets a timestamp after the commit of the data table mutation and thus these mutations won't be seen during the commit. Also, when the index is being built, the data hasn't yet been committed and thus won't be part of the initial index build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)