The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
Answers
can you check what the log says? Thats usually more telling.
Cheers,
Martin
Dortmund, Germany
also the error message location is misleading. The In-Database Processing extension generates a SQL statement and executes it at once. So it can't know what operator caused the error. Therefore, the problem could be with any of the operator settings (or a bug in the extension).
Regards,
Balázs
Mar 4, 2020 11:17:51 AM INFO: No filename given for result file, using stdout for logging results!
with the connection working perfectly.
Cheers
Sven
which version of In-Database Processing are you using? Mine always logs the issued SQL statement. That's what we're interested in (you could redact it if it has sensitive table or column names, but we should see the structure).
Regards,
Balázs
Thanks
Sven
I was asking for the In-Database Processing extension version. I guess that could be different. I have 9.5 and there is no newer version in the Marketplace.
Did you change the process parameter "logverbosity"? Can you look into your database logs if you don't get the SQL from RapidMiner?
I don't have access to the source code of the extension, so I can only make semi-educated guesses on how it works.
Regards,
Balázs
Sven
I don't know but getting the attempted SQL statement is really the best way for us to help you. In-Database Processing is probably generating a wrong SQL statement (or a correct one that's not understood by your database), and you would help future users by telling us the details so the developers can fix it.
As I wrote, the processes I've tried are putting the SQL into the process log. Please try creating a minimal example process and look if that's the case. Then work step by step on reproducing the problem. Or alternatively get the statement and/or the error message from the database server.
Regards,
Balázs
No sql is detected in the process log.
I only get Mar 6, 2020 12:48:23 PM WARNING: Incorrect syntax near '0'.
To be continued.
Thanks anyway!!!!!!