Using Drill JDBC Driver on IBM JDK

Hi,  I have Apache Drill 1.9 running in embedded mode on windows machine using Oracle JDK 1.8. I am trying to connect to Drill using the JDBC driver from an application that will need to use IBM JDK 1.8 because of some other compatibility issue. However, I am getting the following error from

Re: Issue with drill query

Can you file a Drill JIRA? From the stack trace and the relevant code, seems there is a bug in HiveMetadataProvider. sizeInBytes = Long.valueOf(numRowsProp) ==> sizeInBytes = Long.valueOf(sizeInBytesProp); 1.

Re: Issue with drill query

Your query is the longest query I have heard of :) In any case, lets try the below steps : 1. Can you first try your query directly on hive? If hive reports an error during its metadata operations, then you can expect drill to fail as well during planning. 2. Increase the heap memory : Since the

Issue with drill query

Hi all, I hope this is the correct place to ask for help. We have some hive tables stored as textfile that we try to query from, and perform some joins. Because we have programmed a SQL Query generator and based on end user’s selection, it came up with a SQL query that is about 1 million

Re: Problem in WHERE clause querying HBase

Hi Andrea, Thank you for trying out drill and identify the issue. Column names in HBase should be case-sensitive, according to drill doc: https://drill.apache.org/docs/lexical-structure/ Please file a jira to keep track of the issue, and drill dev will fix it. Thanks, Dechang Lexical

Problem in WHERE clause querying HBase

Hi all, I am a newbie in Drill and Hbase. I have installed Hbase 1.2.1 and Drill 1.9.0 both on a embedded (single host) configuration. I have enabled the HBase plugin with default parameters. I have a table that I manage to connect to and retrieve: SELECT CONVERT_FROM(row_key, 'UTF8') as key,

Re: ideal drill node size

I would second John's suggestion that you should try a single large machine, taking care to get your memory settings right. In general, Drill will use both CPU and memory, and in your setup, you will probably get better (and more predictable) performance with a single node setup. As John

Re: Drill Hangout 2/7/2017

Hi Jasbir, Which version of Drill are you using? This issue was fixed in 1.8.0. Please see DRILL-3710 As Jinfeng mentioned, the default value of `planner.in_subquery_threshold` is 20. So you should see the Join plan for ~300 in clause size.

Re: Problem in WHERE clause querying HBase

Hi all again, I have identified the issue and the behavior and the reason for the error: My HBase schema for that column I am trying to select is actually: fogDecDB.Location.Latitute *with a capital "L"* however it gets somehow identified and properly parsed in the SELECT part of the