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 2013/02/17 20:31:12 UTC

[jira] [Resolved] (DRILL-26) Implement Store Reference Operator

     [ https://issues.apache.org/jira/browse/DRILL-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Nadeau resolved DRILL-26.
---------------------------------

    Resolution: Fixed
    
> Implement Store Reference Operator
> ----------------------------------
>
>                 Key: DRILL-26
>                 URL: https://issues.apache.org/jira/browse/DRILL-26
>             Project: Apache Drill
>          Issue Type: New Feature
>            Reporter: Timothy Chen
>            Assignee: Jacques Nadeau
>              Labels: logical
>
> Store (1 K)
> Store the stream output to a storage engine.  The sink parameter references a defined datasource within the logical plan.  The target parameter describes the storage engine specific parameters (e.g. storage type, filename, etc).  The partition values describe how to partition the output data.  Partitioning can be done on a random, hash or ordered basis.  An optional start parameter describes the set of partitions to target.  In the case that starts are not described, the system will determine an appropriate set of partitions based on the nature of the query and its execution plan.   Since the Logical Plan is typically not a direct user interface, outputting to terminal is done through a special type of sink called an rpc sink.  The consumer of the logical plan interface is then responsible for setting up an inbound rpc endpoint with which the execution layer can communicate the results.
> { @id†: <opref>, op: “store”, 
>   input†: <input>, 
>   sink: <string>, 
>   target: <json>, 
>   partition*: {
>     type: <RANDOM|HASH|ORDERED>, 
>     exprs: [<expr>, … <expr>], 
>     starts*: [<expr>, … <expr>]
>   }
> }

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