You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2019/03/12 00:40:00 UTC

[jira] [Comment Edited] (DRILL-7086) Enhance row-set scan framework to use external schema

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

Paul Rogers edited comment on DRILL-7086 at 3/12/19 12:39 AM:
--------------------------------------------------------------

Yes. It is another step toward achieving DRILL-7011. This is the framework support. The next step, in DRILL-7011, will be to link the planner-side work with the schema in the physical plan and pass that into the mechanism created in this PR.


was (Author: paul.rogers):
Yes. It is another step toward achieving DRILL-7011.

> Enhance row-set scan framework to use external schema
> -----------------------------------------------------
>
>                 Key: DRILL-7086
>                 URL: https://issues.apache.org/jira/browse/DRILL-7086
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.15.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Major
>
> Modify the row-set scan framework to work with an external (partial) schema; inserting "type conversion shims" to convert as needed. The reader provides an "input schema" the data types the reader is prepared to handle. An optional "output schema" describes the types of the value vectors to create. The type conversion "shims" give the reader the "setFoo" method it wants to use, while converting the data to the type needed for the vector. For example, the CSV reader might read only text fields, while the shim converts a column to an INT.
> This is just the framework layer, DRILL-7011 will combine this mechanism with the plan-side features to enable use of the feature in the new row-set based CSV reader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)