phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2546) Filters should take into account that multiple versions may be scanned
Date Sun, 27 Dec 2015 08:11:49 GMT

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

James Taylor updated PHOENIX-2546:
----------------------------------
    Attachment: PHOENIX-2546.patch

[~tdsilva] - please review. We should have more tests like the ones I'm adding in TransactionIT
to test that the visibility acts as expected.

> Filters should take into account that multiple versions may be scanned
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-2546
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2546
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>         Attachments: PHOENIX-2546.patch
>
>
> With support for transactions, multiple versions of data will be scanned. The filters
must be careful to advance correctly so that they only deal with the single last version.
Otherwise, the state that they keep inadvertently collects state across multiple versions.

> Note that this depends on https://issues.cask.co/browse/TEPHRA-162 going in to ensure
that the visibility filtering for transactions occurs first and cooperates with other filters.




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

Mime
View raw message