ff Maass <jma...@cccis.com> wrote:
>
>>
>> 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
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.
of disconnection but finally we found there were packet drops.
On Feb 10, 2016 3:39 AM, "Paul Friedman" <paul.fried...@streetlightdata.com>
wrote:
> Thanks for the reply. Since the 2 machines are on the same LAN (no
> firewall in between), does the Drill JDBC driver (or drill-embed
Hello...
I'm executing a long-running Drill (1.4) query (4-10mins) called via JDBC
from Talend and sometimes I'm seeing an error stack like this (see below)
The query is a select statement with an order by against a directory of
Parquet files which were produced by Spark. Probably half the time
eck with firewall settings.
On Feb 10, 2016 12:27 AM, "Paul Friedman"
<paul.fried...@streetlightdata.com>
wrote:
> Hello...
>
> I'm executing a long-running Drill (1.4) query (4-10mins) called via
> JDBC from Talend and sometimes I'm seeing an error stack like t
