I've started playing with Search API Entity Translation v2b on pretty big site with thousands of pretty big entities, and the first issue I'm experiencing is Apache timeout during call to SearchApiEtDatasourceController::getAllIndexItemIds() when I try to enable an index and datasource controller tries to load all those thousands of entities in SearchApiEtDatasourceController::startTracking().
Probably I'll just rewrite the startTracking() method to make it use Batch API, for the moment though having an option to enable such index using Drush would temporarily solve the issue too.
Patch to follow.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | search_api-drush_enable_disable-2093023-2.patch | 3.32 KB | maciej.zgadzaj |
| #1 | search_api-drush_enable_disable-2093023-1.patch | 3.2 KB | maciej.zgadzaj |
Comments
Comment #1
maciej.zgadzaj commentedComment #2
maciej.zgadzaj commentedSlightly more verbose version, with one extra message added in
drush_search_api_enable()right before enabling starts.Comment #3
drunken monkeyI don't use drush, so it's hard for me to test this. But it does make sense to have that command, and if you've tested it thoroughly (also error cases?) then I guess I'll just commit it in a few days. Maybe someone else will even want to review, too.
Comment #4
maciej.zgadzaj commentedYes, error cases too, not many of them possible there though: empty param - processes all indexes, invalid param - displays error message.
Comment #5
drunken monkeyWell, then I'll just take your word for it. ;)
Committed. Thanks a lot for your work!