Hello, fellow drill-ers!
Reposting from the Drill Slack community, under the apache/drill:1.17
docker container, I am having problems querying a parquet file. This file
(possibly generated via pyspark) has an INT64 type field that whenever
included generates an immediate error in the complex parqu
ptions still strikes me as odd. I don't see anywhere these are set in the
shell version of sqlline, but as this definitely seems to work ¯\_(ツ)_/¯
David
On Tue, Mar 7, 2017 at 12:05 PM, David F. Severski
wrote:
> Hi, Kunal.
>
> Part of my problem is that I'm unsure what JVM
to the running Drill JVM to validate that the
> settings were picked up ?
>
>
> Kunal Khatua
>
> Engineering
>
> [MapR]<http://www.mapr.com/>
>
> www.mapr.com<http://www.mapr.com/>
>
>
> From: David F. Severski
>
Greetings!
I'm a new user of Drill 1.9.0 under Windows 10 w/Java 1.8.0_121 (x64). I am
trying to configure drill-embedded to have more direct memory available to
it than the default 7GB I see when starting on my 32GB equipped
workstation. Uncommenting the DRILL_HEAP and DRILL_MAX_DIRECT_MEMORY
set
