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] [Resolved] (PHOENIX-362) Enable a connection to see its own uncommitted data on queries
Date Sun, 24 Jan 2016 04:22:39 GMT

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

James Taylor resolved PHOENIX-362.
----------------------------------
    Resolution: Duplicate

Duplicate of PHOENIX-1674.

> Enable a connection to see its own uncommitted data on queries
> --------------------------------------------------------------
>
>                 Key: PHOENIX-362
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-362
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>              Labels: enhancement
>
> Currently, if you have uncommitted data, you won't see it when you run queries until
it is committed. We could potentially send the uncommitted data over the wire (sending each
region only its own data), expose the following method from HRegion (or something similar):
>     protected RegionScanner getScanner(Scan scan,
>         List<KeyValueScanner> additionalScanners) throws IOException {
> and then add a KeyValueScanner in front of the normal scanner that represents a scan
on the uncommitted data.



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

Mime
View raw message