New issue 32 by mo.j...@gmail.com: '# of records to process' spinner has
not effect in Cleansing Projects
http://code.google.com/p/power-matchmaker/issues/detail?id=32
What steps will reproduce the problem?
1. Create a cleansing project on a table with a large number of rows (in
the thousands)
2. Setup the Transformation (could be as simple as directing all the input
tables back into the
result table)
3. Go to the Run Cleansing Engine screen
4. Make sure you set # of records to process to a non-zero number,
preferably a small number.
5. Select Message Level of DEBUG (doesn't trigger the bug but helps you
observe what's
happening)
6. Click Run Engine
What is the expected output? What do you see instead?
Expected to observe the engine to only process the specified number of
records. Instead, when
you run the engine, it goes to 100% and then keeps going. WIthout a debug
level log, all you'll
see is the bar go to 100% and stop, but with debugging on, you'll notice
the engine is processing
more records ( and these are other different records, not the same ones
over again). This
demonstrates that the record limit isn't working.
I should note that this has only been demonstrated on a Windows 7 machine
running on a SQL
Server 2008 Express instance, but I think this is probably affecting other
platforms as well.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Reproduced this issue with PostgreSQL 8.4 on OS X 10.6.
Comment #2 on issue 32 by mo.j...@gmail.com: '# of records to process'
spinner has not effect in Cleansing Projects
http://code.google.com/p/power-matchmaker/issues/detail?id=32
The problem was CleanseEngineImpl wasn't passing on the row count to the
MungeProcessor. Simple fix.