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/09/21 20:28:04 UTC
[jira] [Created] (PHOENIX-2282) Define serialization of sub scan
for Drill to leverage Phoenix
James Taylor created PHOENIX-2282:
-------------------------------------
Summary: 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
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)