You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2012/11/09 03:56:13 UTC

[jira] [Created] (DRILL-13) Storage Engine: Define Java Interface

Jacques Nadeau created DRILL-13:
-----------------------------------

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

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

[jira] [Comment Edited] (DRILL-13) Storage Engine: Define Java Interface

Posted by "goog cheng (JIRA)" <ji...@apache.org>.
    [ 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 9:13 AM:
----------------------------------------------------------

protocol-buffers or a nosql like couchDB?
                
      was (Author: googcheng):
    protocol-buffers or a nosql ?
                  
> 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

[jira] [Comment Edited] (DRILL-13) Storage Engine: Define Java Interface

Posted by "goog cheng (JIRA)" <ji...@apache.org>.
    [ 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:58 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 ok. Is Storage Engine Read Engine which is to read data from other data sources?  That i got from the paper i would be sorry if there is something error i made
                
      was (Author: googcheng):
    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. Storage Engine is read engine from other data sources?  That i got from the paper i would be sorry if there is something error i made
                  
> 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

[jira] [Commented] (DRILL-13) Storage Engine: Define Java Interface

Posted by "goog cheng (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DRILL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493835#comment-13493835 ] 

goog cheng commented on DRILL-13:
---------------------------------

protocol-buffers or a nosql ?
                
> 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

[jira] [Updated] (DRILL-13) Storage Engine: Define Java Interface

Posted by "Jacques Nadeau (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DRILL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Nadeau updated DRILL-13:
--------------------------------

    Description: 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  (was: 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)
    
> 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

[jira] [Comment Edited] (DRILL-13) Storage Engine: Define Java Interface

Posted by "goog cheng (JIRA)" <ji...@apache.org>.
    [ 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:56 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. Storage Engine is read engine from other data sources?  That i got from the paper i would be sorry if there is something error i made
                
      was (Author: googcheng):
    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
                  
> 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

[jira] [Comment Edited] (DRILL-13) Storage Engine: Define Java Interface

Posted by "goog cheng (JIRA)" <ji...@apache.org>.
    [ 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