Can you tell us what the volume of those files was? How many records, how many
files, how many columns?
Sent from my iPhone
> On Feb 25, 2016, at 7:27 PM, "Edmon Begoli" wrote:
>
> Hello fellow Driilers,
>
> I have been inactive on the development side of the project, as we got busy
> being h
So good to hear Drill is useful in real life.
Chun
> On Feb 25, 2016, at 7:27 PM, Edmon Begoli wrote:
>
> Hello fellow Driilers,
>
> I have been inactive on the development side of the project, as we got busy
> being heavy/power users of the Drill in the last few months.
>
> I just want to sh
Hello fellow Driilers,
I have been inactive on the development side of the project, as we got busy
being heavy/power users of the Drill in the last few months.
I just want to share some great experiences with the latest versions of
Drill.
Just tonight, as we were scrambling to meet the deadline,
Not so short answer:
In Drill 1.5 (I assume you are using 1.5) we have an improved allocator
that better tracks how much memory each operator is using. In your case it
seems that the date has very wide columns that are causing Sort to choke on
the very first batch of data (1024 records taking up 2
Short answer:
increase the value of planner.memory.max_query_memory_per_node, by default
it's set to 2GB, try setting to 4 or even 8GB. This should get the query to
pass.
On Thu, Feb 25, 2016 at 5:24 PM, Jeff Maass wrote:
>
> If you are open to changing the query:
> # try removing the functio
If you are open to changing the query:
# try removing the functions on the 5th column
# is there any way you could further limit the query?
# does the query finish if u add a limit / top clause?
# what do the logs say?
From: Paul Friedman
Sent: Th
I’ve got a query reading from a large directory of parquet files (41 GB)
and I’m consistently getting this error:
Error: RESOURCE ERROR: One or more nodes ran out of memory while executing
the query.
Unable to allocate sv2 for 1023 records, and not enough batchGroups to
spill.
batchGroups.si
Hi,
This query targets Avro files in the latest 1.5 release:
0: jdbc:drill:zk=local> select count(*) from
dfs.asa.`/streaming/venuepoint/transactions/` as s where s.sold_to =
'Customer/4-2492847';
+-+
| EXPR$0 |
+-+
| 5788|
+-+
0: jdbc:drill:zk=local> select count(*)
What is the prescribed / appropriate way to do the below in apache drill?
We want is to do as one can do with elasticsearch:
* Write our rest service endpoint in java
* consume the elasticsearch library
* deploy our application
* have an elasticsearch cluster that also has our code runnin
