Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.
Hanging on SQL Queries
Every now and again (1 in 3 times) Rapidminer will hang on an SQL query. Usually my process will take 5 minutes.
By hang I mean the timer just keeps going, for hours, it never resolves.
The data in the database is static, im not updating/writing new rows to it.
is this a common issue? Should I think about doing a large extract from the database to my local machine and working with that?
I sometimes get this: Feb 4, 2012 6:12:29 PM WARNING: Caught exception in concurrent execution of Read Database (Read Database): com.rapidminer.operator.UserError: Database error occurred: Operation not allowed after ResultSet closed
By hang I mean the timer just keeps going, for hours, it never resolves.
The data in the database is static, im not updating/writing new rows to it.
is this a common issue? Should I think about doing a large extract from the database to my local machine and working with that?
I sometimes get this: Feb 4, 2012 6:12:29 PM WARNING: Caught exception in concurrent execution of Read Database (Read Database): com.rapidminer.operator.UserError: Database error occurred: Operation not allowed after ResultSet closed
Tagged:
0
Answers
Please post the XML.
You're getting an SQL error - "Operation not allowed after ResultSet closed" - the question is why? I Googled that error and followed this link
http://stackoverflow.com/questions/5840866/getting-java-sql-sqlexception-operation-not-allowed-after-resultset-closed
The bit that caught my eye was.. because there is a fair amount of common ground between the two SQL statements. I could imagine scenarios where the second request kicks off at the wrong time, especially if the main process is parallelised http://rapid-i.com/rapidforum/index.php/topic,2162.msg8510.html#msg8510.
As an aside, if we look at the SQL.. In each you are joining the same two tables, in the same way , on school_list_holiday_data.id=school_list_holiday_sources.id ; that could therefore be done in one statement, because you can filter out your training and test sets explicitly in RM. In fact this is a pretty good example of how it is easier to debug SQL using el rapido. Actually I'd do the join in RM as well 8)