NPE running match engine

[GoogleCodeExporter]

I tried to run a match engine in the debug mode and got the following 
exception:

java.lang.RuntimeException: java.lang.NullPointerException
    at 
ca.sqlpower.matchmaker.MatchEngineImpl.call(MatchEngineImpl.java:254)
    at 
ca.sqlpower.matchmaker.swingui.engine.EngineWorker.doStuff(EngineWorker.jav
a:117)
    at ca.sqlpower.swingui.SPSwingWorker.run(SPSwingWorker.java:104)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
    at 
ca.sqlpower.matchmaker.munge.MungeProcessor.call(MungeProcessor.java:71)
    at 
ca.sqlpower.matchmaker.munge.MungeProcessor.call(MungeProcessor.java:62)
    at 
ca.sqlpower.matchmaker.MatchEngineImpl.mungeAndMatch(MatchEngineImpl.java:2
81)
    at 
ca.sqlpower.matchmaker.MatchEngineImpl.call(MatchEngineImpl.java:229)
    ... 3 more

Original issue reported on code.google.com by bdietz.de on 13 Nov 2009 at 4:44

[GoogleCodeExporter]

Just realized I'm getting the error in debug mode and also when I'm not in 
debug mode. 
Will try and figure out more details

Original comment by bdietz.de on 13 Nov 2009 at 4:46

• Changed title: NPE running match engine

[GoogleCodeExporter]

Is this happening with all of your deduping projects or is this only happening 
with this one specific project?

Original comment by mo.j...@gmail.com on 13 Nov 2009 at 4:50

[GoogleCodeExporter]

I think I found the issue. Sometimes DQguru creates a transformation (either 
during 
match or merge) called "Synthetic_Matches" without any steps inside. Running 
the match 
engine again (and having all transformations selected by default) will cause 
the NPE. 
If you exclude the transformation "Synthetic_Matches" you won't have that 
problem.

Original comment by bdietz.de on 13 Nov 2009 at 5:17

[GoogleCodeExporter]

Original comment by bdietz.de on 9 Jul 2010 at 1:51