You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2014/11/14 12:30:33 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=14212153#comment-14212153 ]
Hari Sekhon commented on DRILL-624:
-----------------------------------
This should be configurable via a keyword per SQL query since if you configure it at the storage plugin level then it'll apply to all fields.
Having a session variable for it would also be useful but the query override is non-optional IMHO.
> 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: Future
>
>
> 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.3.4#6332)