Hey John, What do you get when you run "select * from sys.version" ?
extractHeader is false by default, so you need to explicitly set it to true. can you post your storage plugin configuration ? Thanks On Tue, Dec 1, 2015 at 6:04 AM, John Omernik <[email protected]> wrote: > Hey all, > > Per my comment on https://issues.apache.org/jira/browse/DRILL-4145, I am > curious on why a CSV query (I am assuming with a default configuration, but > I have asked the question) in S3 would interpret differently than a CSV > query in MaprFS. > > Per the other user, they are using Drill 1.3, and I am as well (per the > MapR folks, I am using a Dev release version from MapR that has the Office > 1.3 release code base) > > Basically, The query from the JIRA author showed the CSV file being > interpreted, i.e. the "FIELD_1", "FIELD_2" etc were the headers and the > results broken out into columns. When I did this on the same data, I got > one results, columns and an array of data. > > I tried setting extractHeader: true (what is the default on this setting) > and that had no effect. (After I update a storage plugin, what do I need to > do to ensure I see the effect in my SQL line session? DO I need to > reconnect? Basically I set the storage plugin, got the "success" then > changed to a difference schema and then back to my original schema and saw > no effect... should I reconnect or is that not needed?) > > Just curious on why we'd see different ways to read CSV files, the S3 vs. > MapRFS shouldn't be different... or am I missing something? > > Thanks! > > John > -- Abdelhakim Deneche Software Engineer <http://www.mapr.com/> Now Available - Free Hadoop On-Demand Training <http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available>
