[
https://issues.apache.org/jira/browse/DRILL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605694#comment-13605694
]
David Alves commented on DRILL-13:
----------------------------------
Question: What gets pushed below the SE layer? Is that a rewritten logical plan
that the SE will transform into something it can run? or is the plan in some
other form (physical ?)?
Because certain operators get broken down into a portion that executes below
the SE and another that executes above the SE (like aggregation into partial
aggregation + merge or joins into a local join + distributed join) it would
make sense to make the plan passed to the SE the physical one, correct?
Also the plan that is passed as argument to the SE should only include the
relevant portions, correct ?(I mean the header and the ops being executed by
the SE).
Thoughts?
> Storage Engine: Define Java Interface
> -------------------------------------
>
> Key: DRILL-13
> URL: https://issues.apache.org/jira/browse/DRILL-13
> Project: Apache Drill
> Issue Type: Task
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
>
> We're going to need to define a storage engine API. At a minimum, we'll need
> to generate a Java one. We will probably need to also create a CPP one.
> This task is for the former. Things that are likely to be included in a the
> Java interface are: reader (scanner), writer, capabilities interface, schema
> interface, statistics interface, data layout and ordering
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
