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-1900) Increase testing around transaction integration
Date Tue, 01 Sep 2015 18:28:45 GMT

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

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

1. Transaction collision on indexes.

2. See if IndexFailureTest can be modified to test transactions.

> Increase testing around transaction integration
> -----------------------------------------------
>
>                 Key: PHOENIX-1900
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1900
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Thomas D'Silva
>
> Read your own writes testing:
> - UPSERT SELECT when there's uncommitted data being selected.
> - Aggregate queries when there's uncommitted data (see FIXME in TransactionIT.testDelete).
> - Mix of transactional and non transactional data (ensure that non transactional data
is not accidently written).
> Secondary indexes:
> - Ensure writes to local/global mutable/immutable indexes are undone correctly and index
is left in a valid state when transactions overlap. In particular, we'll want to test after
the index data has been written to HBase already in a case that requires point deletes for
an index row. For example, if a covered column has an existing value that's updated, a point
delete would be required to get rid of it make the earlier covered column value visible again.
> - Ensure that in the event of a failure that cannot be aborted by the client, that index
rows are correctly filtered when it's used in a query.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message