Download [#SPAGOBI-433] Data mining process does not throw the END event

[SPAGOBI-433] Data mining process does not throw the END event Created:
06/Jul/10 Updated: 22/Dec/10 Resolved: 20/Dec/10
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
SpagoBI
SERVER/Datamining/Weka
2.5.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug
Davide Zerbetto
Fixed
None
Not Specified
3.0 Alpha
Priority:
Assignee:
Votes:
Major
Andrea Gioia
0
Not Specified
Not Specified
Description
Data mining process does not throw the END event.
Execute "Simple Data Mining" document on test environment in order to reproduce the
problem.
Comments
Comment by Andrea Gioia [ 20/Dec/10 ]
When the event description is longer than 4000 char it cannot be stored in table sbi_events_log.
This usually happens when there are a lot of analytical drivers associated to analytical
document. To quick fix this problem just modify table sbi_events_log in this way ....
ALTER TABLE sbi_events_log MODIFY COLUMN descr VARCHAR(10000);
At code lavel I have added in method "getParameterListDescription" of class
"WekaEngineInstanceMonitor" an extra check to be 100% sure that the engine does not
generate event description longer than 10000 char (see line 113)
P.s. this error was difficult to be traced because the associated DAO throws only EMFUserError
that hide chained exceptions. This type of exception is an example of terrible exception
management and must be deprecated asap.
Comment by Andrea Gioia [ 22/Dec/10 ]
Errata Corrige:
To quick fix this problem just modify table sbi_events_log in this way ....
ALTER TABLE sbi_events_log MODIFY COLUMN descr TEXT;
this because some databases like oracle do not support VARCHAR longer tha 4000 chars
Generated at Sat May 06 18:52:57 CEST 2017 using JIRA 7.2.2#72004sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.