I don't think Oracle as a JDBC data source for Drill is completely functional. A lot of tools like Squirrel will interrogate the Drill metadata and problematic data sources can create some issues. Best to start with simple Drill data sources first till you are sure about the tool to Drill connectivity and functions before adding data source that may be a challenge.
--Andries > On Jan 14, 2016, at 2:51 PM, Timothy Findlay <timothyfind...@nbnco.com.au> > wrote: > > Hi Folks, > > Thanks for the feedback, I kept playing with the URL's and ended up with: > jdbc:drill:drillbit=192.168.56.102:31010 > > Using that I think I might have some insight into the core problem. I omitted > from the initial report was that I had dropped an Oracle JDBC JAR in and > tried to define a connection to Oracle via the Web UI. When Squirrel wouldn't > connect I went digging and looked at the logs where I found this: > 2016-01-14 14:22:42,871 [2968eb7c-87f3-6f40-6f40-fc7005f6ed59:foreman] INFO > o.a.drill.exec.work.foreman.Foreman - Query text for query id > 2968eb7c-87f3-6f40-6f40-fc7005f6ed59: SELECT '' AS `Interim zero-row result > set` FROM INFORMATION_SCHEMA.CATALOGS LIMIT 0 > 2016-01-14 14:23:03,564 [2968eb7c-87f3-6f40-6f40-fc7005f6ed59:frag:0:0] INFO > o.a.d.e.w.fragment.FragmentExecutor - > 2968eb7c-87f3-6f40-6f40-fc7005f6ed59:0:0: State change requested > AWAITING_ALLOCATION --> FAILED > 2016-01-14 14:23:03,568 [2968eb7c-87f3-6f40-6f40-fc7005f6ed59:frag:0:0] INFO > o.a.d.e.w.fragment.FragmentExecutor - > 2968eb7c-87f3-6f40-6f40-fc7005f6ed59:0:0: State change requested FAILED --> > FINISHED > 2016-01-14 14:23:03,597 [2968eb7c-87f3-6f40-6f40-fc7005f6ed59:frag:0:0] ERROR > o.a.d.e.w.fragment.FragmentExecutor - SYSTEM ERROR: IllegalArgumentException: > Unknown SQL type -102 > [Error Id: 6d3a3ec0-1a2a-4d70-8b20-00fe05304d08 on localhost:31010] > org.apache.drill.common.exceptions.UserException: SYSTEM ERROR: > IllegalArgumentException: Unknown SQL type -102 > > When I disabled the Oracle connection, Squirrel worked fine. I haven't worked > out what SQL Type it is complaining about from Oracle yet. I'll dig a bit > deeper and see what I can discover. I found that Drill uses Calcite and the > type mapping appears to be handled in Avatica, so I might need to dig into > that. > > Cheers, > Tim. > > -----Original Message----- > From: Andries Engelbrecht [mailto:aengelbre...@maprtech.com] > Sent: Friday, 15 January 2016 3:20 AM > To: user@drill.apache.org > Subject: Re: JDBC Ignores URL ? > > What ZK are you using , Apache? > > Also the can the client system resolve the hostname of the VM with Drill on > it? > > In simplified terms the connection will work like this. > Client connects to ZK (port 2181 or 5181 pending which ZK is used), ZK > returns the hostname of the VM (not IP) and also which drillbit to connect > to. Client connects to drillbit on port 31010. > > Make sure ZK ports and drill ports are open, and also hostname resolution is > in place (/etc/hosts for Linux/Mac, or /windows/system32/driver/etc/hosts for > windows typically). > > > Also with VMs you need to check if you use NAT or bridged adapter, I prefer > bridged adapter to get a separate IP from the host system. > > > --Andries > > >> On Jan 13, 2016, at 4:48 PM, Timothy Findlay <timothyfind...@nbnco.com.au> >> wrote: >> >> Hi, >> >> I know this sounds crazy, but here is how I got the problem. >> >> - I downloaded Drill 1.4.0 and dropped it in a Centos VM (Virtualbox) >> >> - Configured Zookeep, Started Drill service (daemon) >> >> - Tested using SQLLine, all good. >> >> - Picked the drill-jdbc-all-1.4.0.jar from the JAR's folder >> >> - Started Squirrel as described. Added the driver, with the JAR, set >> the Driver name >> >> - Created an Alias and set the URL to >> jdbc:drill:zk=192.168.56.102:2181 >> >> - Trying to connect I get Caused by: >> oadd.org.apache.drill.exec.rpc.RpcException: CONNECTION : >> java.net.ConnectException: Connection refused: no further information: >> localhost/127.0.0.1:31010 >> >> I've checked the VM, there's no firewall or anything stopping it. But if you >> look closely, where the heck is it getting port 31010 from ? and Drill is >> running on a VM, not localhost. >> >> What gives ? How can I put in configuration details and it seems to ignore >> them. >> >> Any hints/tips would be appreciated. >> >> Tim. >
