drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Dunning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-13) Storage Engine: Define Java Interface
Date Fri, 11 Jan 2013 01:07:12 GMT

    [ https://issues.apache.org/jira/browse/DRILL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550657#comment-13550657
] 

Ted Dunning commented on DRILL-13:
----------------------------------

I think that this misses what we need.  The actual storage substrate is something that Drill
shouldn't care about.

What Drill cares about is:

- how are records read?

- is the data stored in columnar fashion?

- what is the schema for the data?

- are there multiple views of the data (for instance if the scanner does side effecting columnization)?

- is there locality information available?

I think that the reference interpreter will be clarifying many of these issues.

                
> 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
>
> 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

Mime
View raw message