Closed mariczone closed 8 years ago
We made it that way.
Delete operation as well as approve/disapprove is done by removing or adding records from/into the Lucene index. That is quite a slow operation; you won't notice it if records are just few, but with thousands of records the latency is quite noticeable (and annoying).
However, a background task 'CatalogSynchronizer' will update Lucene index once the job is finished, i.e. all the undesired records will be deleted from the index. More about it here: https://github.com/Esri/geoportal-server/wiki/All-gpt.xml-file-settings#Scheduler_Settings
I hope it helps.
Geoportal 1.2.6 Apply "delete" with Apply action to the entire results set will only delete data in database but not in lucene index. It still can searchable via Geoportal after removed.
Is anyone can confirm this is bug? Thank you.