Hi Piotr,
You might have to wait till 1.2 comes out. There's a patch outstanding
that needs to be updated and merged that should address this issue.
Parth
On Sun, Aug 16, 2015 at 8:06 AM, Piotr Sokólski wrote:
> Hi.
> I’m using calcite-core 1.2 in my project. Importing the Drill driver into
>
Drill should work on Cloudera and other distributions. You can refer to
https://drill.apache.org/docs/file-system-storage-plugin/ for details on
configuring a distributed file system plug-in.
Can you try specifying the IP address of the primary namenode instead of
"nameservice-ha" in the DFS stora
BTW, I tried to use
https://repository.apache.org/content/repositories/snapshots/org/apache/dri
ll/exec/drill-jdbc-all/1.2.0-SNAPSHOT/drill-jdbc-all-1.2.0-20150816.183803-
1.jar and it resulted in java.lang.NoClassDefFoundError:
oadd/java/sql/Driver
On 8/18/15, 6:50 PM, "Kartik Bhatia" wrote:
Hi,
I installed Apache Drill to run on a Cloudera cluster which has HA.
However, hive queries are failing with "Unknown Host exception -
nameservice-ha" error because Drill is unable to resolve nameservice-ha
which is part of Cloudera.
Is this a known issue or I can do some setup to make it work
Edit:
Here is the error:
Error: SYSTEM ERROR:
org.apache.drill.common.exceptions.DrillRuntimeException: Error in parquet
record reader.
Message:
Hadoop path: /data/1440002040405/part-r-1.parquet
Total records read: 0
Mock records read: 0
Records to read: 32768
Row group index: 0
Records in ro
We can't see the error that I guess you posted as an image. Images don't
work on the list.
Kristine Hahn
Sr. Technical Writer
415-497-8107 @krishahn skype:krishahn
On Wed, Aug 19, 2015 at 9:55 AM, Usman Ali
wrote:
> Hi,
>I received following error while querying a parquet file stored o
Hi,
I received following error while querying a parquet file stored on
S3.
Any Help?
Regards,
Usman Ali
JIRA opened : https://issues.apache.org/jira/browse/DRILL-3671
Le Mardi 18 août 2015 19h28, Jinfeng Ni a écrit :
If the query remains infinitely in PENDING status, and you did not get a
Physical Plan, that might indicate a bug in the sql planner & optimizer.
You may open a JIRA, an
