It is working now. Thanks for the suggestions. It was a matter of getting the 
user credentials working for my database. I only wish the error messages were 
more descriptive, and specific to the failure reason. Glad you opened that 
ticket, Chris.

Thanks,
Scott Wilburn


-----Original Message-----
From: Andries Engelbrecht [mailto:[email protected]] 
Sent: Thursday, March 24, 2016 08:47 AM
To: [email protected]
Subject: [E] Re: JDBC storage plugin fails

I have also seen this fail if the supplied credentials are not valid.

With MySQL it can be a bit tricky as credentials can depend on the location of 
the client, so make sure the MySQL user credentials are for % since Drill is a 
distributed system and any of the nodes may connect to MySQL.

--Andries

> On Mar 24, 2016, at 8:39 AM, Christopher Matta <[email protected]> wrote:
> 
> Scott,
> Could you paste the JSON you're using to define the MySQL storage 
> plugin here? I've experienced that you get that error when either the 
> JSON is invalid, or Drill can't find the class you defined.
> 
> I've created a JIRA to improve this functionality:
> https://issues.apache.org/jira/browse/DRILL-4533
> 
> 
> 
> On Thursday, March 24, 2016, Wilburn, Scott 
> <[email protected]> wrote:
> 
>> Hello,
>> I am trying to connect to a mysql database using the jdbc storage 
>> plugin using Drill 1.5 described here:
>> https://drill.apache.org/docs/rdbms-storage-plugin/
>> 
>> When I try to create the plugin through the web UI, I get the 
>> following vague error:
>> "Please retry: error (unable to create/ update storage)"
>> 
>> I tried to see if more information exists in the drillbit logs, but 
>> didn't see anything relevant. Does anyone know where I can find a 
>> better description of the problem, or is JDBC just broken in 1.5? I 
>> found the following Jira with the same description for 1.2 
>> (DRILL-3977). Has it been broken since 1.2, or am I doing something stupid?
>> 
>> Any help would be appreciated.
>> 
>> Thanks,
>> Scott Wilburn
>> 
>> 
> 
> --
> Chris Matta
> [email protected]
> 215-701-3146

Reply via email to