Re: [ANNOUNCE] Apache Drill release 1.13.0

Congratulations everyone, on yet another great release of Apache Drill! On Mon, Mar 19, 2018 at 6:57 AM Parth Chandra wrote: > On behalf of the Apache Drill community, I am happy to announce the > release of > Apache Drill 1.13.0. > > For information about Apache Drill, and to

RE: QSQL via jdbc (python3 and JayDeBeApi) wraps with SELECT ... LIMIT 0

I'm actually seeing this with JayDeBeApi on Drill 1.13 JDBC driver as well. However, the Drill 1.13 JDBC driver, when used by itself, doesn't issue such a request. I'll need to see if JayDeBeApi is indeed putting a wrapper around non-select queries and a way to disable that. On 3/18/2018

[ANNOUNCE] Apache Drill release 1.13.0

On behalf of the Apache Drill community, I am happy to announce the release of Apache Drill 1.13.0. For information about Apache Drill, and to get involved, visit the project website [1]. This release of Drill provides the following new features and improvements: - YARN support for Drill

QSQL via jdbc (python3 and JayDeBeApi) wraps with SELECT ... LIMIT 0

Hi all, I am attempting to send a query from python3 via JayDeBeApi and am encountering the issue that the SQL is enclosed in a SELECT * FROM $myquery LIMIT 0 With: conn = jaydebeapi.connect("org.apache.drill.jdbc.Driver", "jdbc:drill:drillbit=$mycluster:$myport",

Re: QSQL via jdbc (python3 and JayDeBeApi) wraps with SELECT ... LIMIT 0

Hi Francis, The code below worked for me. Also, I don’t know if it matters, but did you mean to create two cursors? — C import jaydebeapi import pandas as pd #Create the connection object conn = jaydebeapi.connect("org.apache.drill.jdbc.Driver",

RE: QSQL via jdbc (python3 and JayDeBeApi) wraps with SELECT ... LIMIT 0

This error looks familiar and might be because of the Python library wrapping a select * around the original query. Using the JDBC driver directly doesn’t seem to show this problem. Drill 1.13.0 is out now. Could you give a try with that and confirm if the behavior is the same? -Original