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-2282) Define serialization of sub scan for Drill to leverage Phoenix
Date Thu, 01 Oct 2015 18:47:27 GMT

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

James Taylor resolved PHOENIX-2282.
-----------------------------------
    Resolution: Fixed
      Assignee: Jacques Nadeau

Closing as we now have PhoenixScans that serialized the required scan information.

> Define serialization of sub scan for Drill to leverage Phoenix
> --------------------------------------------------------------
>
>                 Key: PHOENIX-2282
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2282
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Jacques Nadeau
>              Labels: drill
>
> I think there are two pieces:
> - the separate parallel unit (always a Scan for Phoenix)
> - the reader class to instantiate that will interpret the results.
> It be pretty easy to write code that combines multiple Scans together too, based on the
start row/end row in the case that Phoenix over-parallelizes due to guideposts.
> FWIW, even the Phoenix DML (UPSERT SELECT and DELETE) fit this model of a Scan plus the
reader code which would push the data back out for the writes (see UpsertCompiler and DeleteCompiler).



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

Mime
View raw message