Numerous fixes have gone into Drill since then. Can you try with Drill 1.12 ?
-Original Message-
From: Siva Gudavalli [mailto:gudavalli.s...@yahoo.com.INVALID]
Sent: Wednesday, February 14, 2018 6:23 PM
To: user@drill.apache.org
Subject: Drill 1.10 Memory Leak with CTAS + partition by
He
Hello,
I am having an issue with CTAS used along with PARTITION BY.
I see there is memory leaked by query. Is this a known Bug? I am on Drill
1.10.0.201707281514
0: jdbc:drill:schema=dfs> CREATE TABLE by_yr (yr, ngram, occurrances) PARTITION
BY (yr) AS SELECT columns[1] yr, columns[0] ngram
Hi Anup,
You may try setting configuration option
'exec.java.compiler.exp_in_method_size' to lower value from default of 50 and
run the query to see if it helps. Even lowering to a value of 1 doesn't help,
the query details and stack trace may helpful for analysis as Khurram mentioned.
alter
I won't be the best source for explaining why the flag worked, but this thread
should help explain why performance is expected to be better when using the
Native Parquet reader.
https://lists.apache.org/thread.html/6429051d5babb87d3b03494524c1802f75d572d630cb5690fd616741@
That said, there is w
Can you please share the exact query as is (without formatting) here. And the
error that you see on Drill 1.11.0, so we can try and repro it.
Thanks,
Khurram
From: Anup Tiwari
Sent: Wednesday, February 14, 2018 3:14:01 AM
To: user@drill.apache.org
Subject: Re:
Hi Team,
Do we have any updates on this? It is coming even in Drill 1.11.0 and i tried
same query on hive, it is working perfectly.
On Fri, Mar 25, 2016 2:30 AM, Jacques Nadeau jacq...@dremio.com wrote:
Looking at the trace it looks like Drill is correctly using the JDK
compiler which is
Hi Kunal,
That issue was related to container size which is resolved and now its
working.However i was trying vice-versa which is a table is created in
hive(2.1.1)/hadoop(2.7.3) and stored on s3 and i am trying to read it via
drill(1.10.0).
So initially when i was querying parquet data stored on s3
Hi Arjun,
Thanks!! This worked and now i am able to query s3. But i didn't understand your
last line and also how this worked with 2.7 jar. Can you please explain this a
bit or provide any reference link?
@padma, i was trying to build from source and executed below steps but got error
:-
JAVA Versi
