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/27 09:04:49 UTC
[jira] [Updated] (PHOENIX-2546) Filters should take into account
that multiple versions may be scanned
[ https://issues.apache.org/jira/browse/PHOENIX-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-2546:
----------------------------------
Description:
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.
was: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.
> 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
>
> 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)