Hi !
I've just tested the new release 2.5 of CloverETL engine.
I found an issue with the DATAINTERSECTION component.
Indeed ...
before in the main processing loop of execute method :
in 2.5 :
the problem occurs when the two input (maybe only one) tables are empty there's a null pointer exception. It was better before cause you didn't go in the loop if there were not input records.
What do you think ?
I've just tested the new release 2.5 of CloverETL engine.
I found an issue with the DATAINTERSECTION component.
Indeed ...
before in the main processing loop of execute method :
while (runIt && driverRecord != null && slaveRecord != null) {
}
in 2.5 :
do {
}while (runIt && (driverReader.hasData() || slaveReader.hasData()));
the problem occurs when the two input (maybe only one) tables are empty there's a null pointer exception. It was better before cause you didn't go in the loop if there were not input records.
What do you think ?
-
Hi, this is really bug; I report the issue to the Mantis bug tracker (http://bug.cloveretl.org/view.php?id=852).
Please sign in to leave a comment.
Comments 1