Don't call ES index refresh after every document added in search:populate
|Assignee:||Mike Gale||% Done:|
|Category:||Search / Browse|
|Target version:||Release 2.3.0|
|Google Code Legacy ID:||Tested version:||2.3|
Right now we're calling ES refresh after adding every document. I think this is unnecessary and just reduces performance, and was just a mistake I made when fixing the "1" search:populate bug.
#3 Updated by Mike Gale about 6 years ago
- Status changed from Feedback to Verified
I don't think we need someone to QA this specifically besides my tests; we do search:populate so often for so many different AtoM instances, if this creates a bug, we'll know about it pretty quickly.