Working in eclipse but has errors with command line

CloverDX Platform
1

Hello I’m really new to clover and I’m guessing I’m just making an easy mistake…

I currently have a really simple graph defined that merges a CSV and a mysql db table and puts the results in another table. I’m using the eclipse plugin (from the marketplace) and when I run the graph from within eclipse it works brilliantly. However, if I try to run the graph using the command line tools I get really strange errors and even after extensive testing I’m not sure what’s going on. For instance, when it parses the UniversalDataReader I get this debug message in the logs: “This parser can’t be used because of the ‘quotedStrings’ feature” and then the speed is set to null. Through trial and error I’m also having issues with the skipRows attribute as well. Even if I turn those off (which I really can’t since then it would parse the CSV wrong) I get this exception as well: “CheckConfig warning: Parameter metadata not available for the given statement
java.sql.SQLException: Parameter metadata not available for the given statement”.

I’m using the latest community edition of clover as well as the latest version of java (clover 3.1.0 / jdk-6u26).

If anybody could help shed some light on the situation I would be very grateful. Thanks.

2

Hello,
both messages in log are only informative and have no influence on the graph execution itself. DataReader can use different parsers (see parser attribute) and during initialization it checks which parser would be the best one for current settings. It starts checking from the simplest parser and if a just checking parser can’t be used, writes this information to the log. The second message is returned by mysql jdbc driver during checking graph configuration and only inform user, that some configuration can be really checked. Both messages appears in the log as well when running the graph from Eclipse (you may need to change the default log level to see them).
And what is the problem with skipRows attribute?

3

Oh okay that makes sense now, thanks for the clarification I thought I was screwing something up! The skiprow error is a non-issue; I was just getting the same message that quotedStrings was giving when I removed that attribute.