Harvester db errors due to fixed character length overflow
In a recent release of Metacat (1.9.0), the Harvester property names were
refactored to begin with the prefix 'harvester.'. Some of Harvester property
names are used as operation codes in metacat's 'harvest_log' table,
'harvest_operation_code' field, which is declared with a fixed length of 30
characters. The 'harvester.ValidateHarvestListSuccess' code is 35 chars, which
exceeds the limit and results in DB errors on record insertion during a harvest.
#1 Updated by Matt Jones about 10 years ago
We need a junit test suite that exercises the full harvester functionality so that future releases don't gave this same problem. Is there one that I'm not aware of, and if so, can it be augmented to run the full harvester Ali with both valid and invalid inputs?
#2 Updated by Duane Costa about 10 years ago
A harvester JUnit test suite does exist in directory:
In its current state, it's able to test much of the harvester's core functionality, but it does need augmentation to cover all potential inputs, such as writing to the log table (as occurred with this bug).