Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Thanks for your help Jacques! Sorry have been out of action for a couple of days. On 7 November 2015 at 18:27, Jacques Nadeau wrote: > Glad you've made some progress. > > Not sure why your .public is how you have to go about things. > Will have to give that some more

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Ok so after a bit of faffing I've made some progress! I had a later version of the storage driver than you had in your pom.xml but that turned out to not matter. The problem was to do with how I was accessing the schema. It seems like for postgres at least I need to go through .public to get to

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Sorry Jacques, one last question for now - whats the best way for me to get setup for (1)? Is calcite forked within the drill repo or do I need to pull both projects locally and statically deploy jars from my fork of calcite to test in drill? Or can I test calcite in isolation? Cheers. On 7

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Glad you've made some progress. Not sure why your .public is how you have to go about things. Will have to give that some more thought. At least you're over that hurdle for the minute. > 1. Uuid columns in postgres arent supported - I'll look to contribute code > to add support for this if its

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Thanks Jacques, I'm a little further - I can now add the postgres storage and I'm no longer getting the NullReferenceException. However, I've got almost as much of a confusing error message (with exec.errors.verbose turned on): 0: jdbc:drill:zk=local> SELECT * FROM customers.profile; Nov 06, 2015

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

I'm not sure what the problem is. I was able to query successfully on my local machine using the same pattern. Here is my configuration so you can see if there is something different. https://github.com/jacques-n/drill/commit/8bd3289b0f5abbcabf33820297e7701d1da76ca0 Do you see anything

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Ah - good pointer, ok I've gotten a little further - I can 'USE' the right database and can see my tables now... Before trying drill with any of my more complicated tables I've created a simple one with 'normal' types: CREATE TABLE "test_table" ( "id" integer not null default

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

What do 'show databases' display? If you do 'use customers' and 'show tables', what does that display? -- Jacques Nadeau CTO and Co-Founder, Dremio On Fri, Nov 6, 2015 at 3:41 PM, Kieran Benton wrote: > Thanks Jacques, > I'm a little further - I can now add the postgres

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

He Kieran, There were some issues with the 1.2 JDBC storage plugin. It had issues with certain data types including TEXT/BLOB. We're in the process of releasing version 1.3 of Drill which should solve many of these issues. Can you try the current release candidate of Drill 1.3 to see if that

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Hi Jacques, Do you know if the 1.3 release addresses the JDBC issues that appeared to be related to MSSQL's three part naming? Thanks, Eric On Fri, Nov 6, 2015 at 2:48 PM, Jacques Nadeau wrote: > He Kieran, > > There were some issues with the 1.2 JDBC storage plugin. It

Re: Apache Drill 1.2 targetting JDBC / postgresql storage

Thanks Jacques, I'll give that a go later tonight. Couple of follow up questions... 1. Is there anything I can do to up the logging and so be able to track these kinds of issues myself and maybe contribute fixes back? 2. Im trialling using some fairly exotic types in postgres, mainly arrays and