phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ohad Shacham (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-4232) Hide shadow cell and commit table access in TAL
Date Mon, 02 Oct 2017 13:55:00 GMT

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

Ohad Shacham reassigned PHOENIX-4232:
-------------------------------------

    Assignee: Ohad Shacham

> Hide shadow cell and commit table access in TAL
> -----------------------------------------------
>
>                 Key: PHOENIX-4232
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4232
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Ohad Shacham
>              Labels: omid
>
> Omid needs to project the shadow cell column qualifier and then based on the value, filter
the row. If the shadow cell is not found, it needs to perform a lookup in the commit table
(the source of truth) to get the information instead. For the Phoenix integration, there are
likely two TAL methods that can be added to handle this:
> # Add method call to new TAL method in preScannerOpen call on coprocessor that projects
the shadow cell qualifiers and sets the time range. This is equivalent to the TransactionProcessor.preScannerOpen
that Tephra does. It's possible this work could be done on the client side as well, but it's
more likely that the stuff that Phoenix does may override this (but we could get it to work
if need be).
> # Add TAL method that returns a RegionScanner to abstract out the filtering of the row
(potentially querying commit table). This RegionScanner would be added as the first in the
chain in the NonAggregateRegionScannerFactory.getRegionScanner() API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message