You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Steven Phillips (JIRA)" <ji...@apache.org> on 2014/06/11 10:41:01 UTC

[jira] [Commented] (DRILL-624) Use Header rows (if exists) as metadata for the text readers

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

Steven Phillips commented on DRILL-624:
---------------------------------------

You could explain in more detail what the desired query experience is?

One way to do this would be to have an option in the format plugin config, "hasHeader", which, if true, will tell the reader to use the first line as a header.

Another option would be to have a SESSION or SYSTEM option that would apply as long as that option is set to true.

> Use Header rows (if exists) as metadata for the text readers
> ------------------------------------------------------------
>
>                 Key: DRILL-624
>                 URL: https://issues.apache.org/jira/browse/DRILL-624
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Storage - Text & CSV
>            Reporter: Neeraja
>            Assignee: Steven Phillips
>             Fix For: 1.0.0-BETA1
>
>
> Currently the text readers return the data as array all the time. A lot of times, the source text files can have header rows which identify the field names/metadata for the data. 
> If this exists, Drill should leverage it to provide the query experience on this metadata directly (just like parquet or JSON).



--
This message was sent by Atlassian JIRA
(v6.2#6252)