Harvester / Remove records by harvester UUID

[fxprunayre]

When harvester contains lot of records, remove records take a while or could even return heapspace errors.

Try to improve performances by using delete by query (instead of loop on each records) eg. 1500 records

• Select > Delete all = 2min
• Harvester > Remove records = 700ms

This will bypass events but maybe that is fine for harvested records?

Maybe there is better JPA alternative for this kind of query?

Checklist

• [x] I have read the contribution guidelines
• [ ] Pull request provided for main branch, backports managed with label
• [ ] Good housekeeping of code, cleaning up comments, tests, and documentation
• [ ] Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• [ ] Clean commit messages, longer verbose messages are encouraged
• [ ] API Changes are identified in commit messages
• [ ] Testing provided for features or enhancements using automatic tests
• [ ] User documentation provided for new features or enhancements in manual
• [ ] Build documentation provided for development instructions in README.md files
• [ ] Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

Funded by Ifremer

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[fxprunayre]

1. Metadata harvested with the GeoNetwork ‘protocol’ in MEF format, may store files in the data directory. In this case, the files should be deleted also.

Indeed, also harvesting WMS most of the time produce thumbnails in the datadir.