Hello Anup,
I could not repro the issue with my data, can you please share the data that
you used so I can try it again with your data.
Thanks,
Khurram
From: Anup Tiwari
Sent: Monday, February 19, 2018 3:09:22 AM
To: user@drill.apache.org
Subject: Re: Code t
Andries's solution is quite handy for the occasional use. But, having a storage
plugin available can be more convenient and will perform better. When used with
table functions, the format plugin allows specifying fields and column names
per-query if you find yourself querying multiple different
Hi Flavio,
Great question! I've not yet experimented with the solution myself, but I
believe that the plugin can be placed into a jar, along with the needed Drill
config file, and then placed into the jars/3rd-party directory if you keep your
config information in the Drill product directory. Pe
I agree... Using Andries' solution in combination with a view is probably the
best approach.
-Original Message-
From: Flavio Pompermaier [mailto:pomperma...@okkam.it]
Sent: Tuesday, February 20, 2018 1:47 PM
To: user@drill.apache.org
Subject: Re: Fixed-width files
Actually what I'd like
Actually what I'd like to achieve, in the end, is to remember how to read a
fixed-width file.
After considering all your opinions, the best way to achieve this will be
probably to create a VIEW and then extract through a DESCRIBE query the
columns definition. What do you think?
On 20 Feb 2018 20:2
If you have Hive storage plugin enabled, You can create Hive table with regex
serde and query the same in Drill.
-- Table contents
$ hadoop fs -cat /tmp/regex_test/*
112123
$
-- Hive DDL with regex '(.{1})(.{2})(.{3})' - column1 of width 1,column2 of
width 2 and column3 of width 3
CREATE EX
This might be a better option, since DRILL-6170 will introduce a rigid parsing
definition. So, different fixed-width files can't leverage the same definition,
though they might share the same extension.
Thanks, Andries!
-Original Message-
From: Andries Engelbrecht [mailto:aengelbre...@
You can also try and see if you can just use the CSV plugin to read a line as
columns[0] and then use the substr function to pull out the fields in the line.
http://drill.apache.org/docs/string-manipulation/#substr
Here is a simple example
Simple csv file
[test]$ cat test.csv
col1col2col3
jdb
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to a user@ or
dev@ list of one or more Apache Software Foundation projects.)
We’re pleased to announce the upcoming ApacheCon [1] in Montréal,
September 24-27. This event is all about you — the Apache project com
For the moment I've created an improvement issue about this:
https://issues.apache.org/jira/browse/DRILL-6170
On Tue, Feb 20, 2018 at 9:23 AM, Flavio Pompermaier
wrote:
> Thanks Paul for this suggestion, I think I'm going to give it a try.
> Once I've created my EasyFormatPlugin where should I p
Thanks Paul for this suggestion, I think I'm going to give it a try.
Once I've created my EasyFormatPlugin where should I put the produced jar?
in which folder within jars directory?
On Tue, Feb 20, 2018 at 2:57 AM, Paul Rogers
wrote:
> It may be that by "fixed width text", Flavio means a file i
11 matches
Mail list logo
