drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "goog cheng (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DRILL-13) Storage Engine: Define Java Interface
Date Fri, 09 Nov 2012 13:54:11 GMT

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

goog cheng edited comment on DRILL-13 at 11/9/12 1:52 PM:
----------------------------------------------------------

protocol-buffers and a nosql like couchDB? do we really need a database to store the columnar
representation data? It seems a distributed filesystem like GFS is good. That i got from the
paper, i would be sorry if there is something error i made
                
      was (Author: googcheng):
    protocol-buffers or a nosql like couchDB?
                  
> 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