Anthony, You could also try enabling debug logging to see what managers are being loaded (if any). This can normally be done by adding "--verbose" to your list of arguments. I'm not sure how it will work with your intended use case.
-Abe On Wed, Jun 19, 2013 at 7:57 AM, Jarek Jarcec Cecho <[email protected]>wrote: > Hi Anthony, > I'm glad to see your interested in Sqoop project! I have to mention that > whereas the direct usage of the Sqoop classes might work, it's not > officially supported API and you might hit some issues along the way. > > I would strongly suggest to upgrade to latest Sqoop version as the 1.4.0 > is quite old. In most cases using the --driver parameter is not needed as > it will instruct Sqoop to use the Generic JDBC Driver instead of > specialized MySQL connector, I would suggest to drop this parameter > entirely. > > Jarcec > > On Wed, Jun 19, 2013 at 03:25:51PM +0900, corbacho anthony wrote: > > Hello, > > > > I am trying to use Sqoop in an osgi pluging but it wont work and I dont > > know why. > > I keep getting the following error: > > "2013-06-19 13:53:27,556 | ERROR | qtp122715895-276 | BaseSqoopTool | ? > ? > > | - - | Got error creating database manager: java.io.IOException: No > > manager for connect string: jdbc:mysql://...." > > > > I have include sqoop in my pom (1.4.0-cdh4b1) and I also have my mysql > > driver loader (i can use in the code). > > > > the part who throw an exception is: > > > > String[] str = { > > "import", > > "--driver", "com.mysql.jdbc.Driver", > > "--connect", "jdbc:mysql://___MY_DB___", > > "--hadoop-home", __HOME__, > > "--query", "Select [.....] AND $CONDITIONS", > > "--split-by", "id", > > "--target-dir", "hdfs://__SERVER__/__FOLDER__", > > "--username", "foo", > > "--password", "barou"}; > > > > return Sqoop.runTool(str); > > > > Thanks, > > Anthony >
