[
https://issues.apache.org/jira/browse/DRILL-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057056#comment-17057056
]
Arina Ielchiieva edited comment on DRILL-7601 at 3/11/20, 2:42 PM:
-------------------------------------------------------------------
Merged into master with commit id 88a84b9d088dad549e8489c487c55c9d7aecff9a.
was (Author: arina):
Merged with commit id 88a84b9d088dad549e8489c487c55c9d7aecff9a.
> Shift column conversion to reader from scan framework
> -----------------------------------------------------
>
> Key: DRILL-7601
> URL: https://issues.apache.org/jira/browse/DRILL-7601
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.17.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Major
> Labels: ready-to-commit
> Fix For: 1.18.0
>
>
> At the time we implemented provided schemas with the text reader, the best
> path forward appeared to be to perform column type conversions within the
> scan framework including deep in the column writer structure.
> Experience with other readers has shown that the text reader is a special
> case: it always writes strings, which Drill-provided converters can parse
> into other types. Other readers, however are not so simple: they often have
> their own source structures which must be mated to a column reader, and so
> conversion is generally best done in the reader where it can be specific to
> the nuances of each reader.
> This ticket asks to restructure the conversion code to fit the
> reader-does-conversion pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
