You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:18:05 UTC

[jira] [Resolved] (PHOENIX-601) Fixing handling of deletes in ApplyAndFilterDeletesFilter

     [ https://issues.apache.org/jira/browse/PHOENIX-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid resolved PHOENIX-601.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Fixing handling of deletes in ApplyAndFilterDeletesFilter
> ---------------------------------------------------------
>
>                 Key: PHOENIX-601
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-601
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Jason Yates
>
> It was causing an infinite loop when there were duplicate CFs added to the filter.
> Further, it wasn't handling the delete/put ordering correctly, which later lead
> to incorrect indexes being constructed in the tests.
> Allows removal of the "destroy tables" stuff in MutableIndexTest, since handle the Phoenix 'table delete' tombstones properly.



--
This message was sent by Atlassian JIRA
(v6.2#6252)