phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2478) Rows committed in transaction overlapping index creation are not populated
Date Wed, 02 Dec 2015 19:14:10 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036406#comment-15036406
] 

Thomas D'Silva commented on PHOENIX-2478:
-----------------------------------------

Would using a wildcard row key allow DML operations that write two different rows to succeed?
Seems like the last alternative which allows read/read conflicts but doesn't allow read/write
or write/write is required for that scenario to work.

> 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)

Mime
View raw message