Re: Drill 1.6 on MapR cluster not using extractHeader ?

One correction: The new text reader is turned on (set to true) by default. I was confused with the doc (which asked user to set the option - but it does mention that the value is true by default). On Mon, Apr 18, 2016 at 11:06 AM, Abhishek Girish wrote: > Firstly, I don't

Re: Drill 1.6 on MapR cluster not using extractHeader ?

Firstly, I don't think this is a default setting, so you will need to explicitly add this under every text format plugin ("csv", "tsv", ...), and inside every dfs storage plugin (if you have more than one). Later turn on the new text reader system/session option, before you can query. Secondly,

Re: Drill 1.6 on MapR cluster not using extractHeader ?

I found that the dfs storage section for csv file types did not all have the extractHeader setting in place. Manually putting it in all four of my nodes may have resolved the issue. In my vanilla Hadoop 2.7.0 setup on the same servers, I don't recall having to set it on all nodes. Did I

Re: Drill 1.6 on MapR cluster not using extractHeader ?

Hello, This is my format setting: "csv": { "type": "text", "extensions": [ "csv" ], "extractHeader": true, "delimiter": "," } I was able to extract the header and get expected results: > select * from mfs.tmp.`abcd.csv`; +++++ | A

Drill 1.6 on MapR cluster not using extractHeader ?

With files in the local filesystem, and an embedded drill bit from the download on drill.apache.org, I can successfully query csv data by column name with the extractHeader option on, as in SELECT customer_if FROM `file`; But in a MapR cluster (v. 5.1.0.37549.GA) with the data in MapR-FS, the