Using the DB backend, I get 0/0 indexed items. Both for nodes as for custom entities. If I save an entity, the fields get indexed though. Overview page will still say 0/0.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2609200-9-indexing-skipped.patch | 613 bytes | christianadamski |
Comments
Comment #2
christianadamski commentedsearch_api_item table is empty.
Comment #3
nick_vhIt is working here. Can you please post steps to reproduce?
Comment #4
christianadamski commentedNot much to say. Using the latest Dev-release, my existing two indexes for custom entites would simply show 0/0 after clearing the existing index. I went on to completely delete server and indexes and just used a Server with default settings and an index for all nodes (there were some) and I still got 0/0.
When the custom indexes where still there, I saved an entity and saw the fields correctly showing up in there respective search_api_xx tables, but search_api_item stayed empty.
I did a complete drush un-install and enable of search_api. Drush updatedb was also executed. Monday I will try a complete re-install of Drupal as a whole.
Comment #5
christianadamski commentedAfter a complete reinstall, it seems to work fine again. No idea what the issue was.
Comment #6
christianadamski commentedI am now at the same situation again. I could already track this down to
datasource/ContentEntity.php line 513 'tracking_page_size' getsing assigned NULL.
Which creates a select Query with range 0:0 which results in 0 items.
$page_size = $this->getConfigValue('tracking_page_size');
$select->range($page * $page_size, $page_size);
Comment #7
christianadamski commentedComment #8
christianadamski commentedOkay, I think I found the issue:
datasource/ContentEntity.php line 512 is if(isset($page)) ...
However: $page might be '0' at this point, which does evaluate as 'isset' but will cause an empty range.
Replacing the if(isset($page)) instead with if(!empty($page)) makes the thing work.
But: I have issues indexing right now for different reasons. Those things might be related. I will keep checking.
Comment #9
christianadamski commentedA one-line-patch attached.
Comment #10
christianadamski commentedComment #11
drunken monkeyThe issue is probably just that you updated to the latest module version, which contains a new configuration setting (
tracking_page_size) whose default won't get set automatically this way.Try executing the following (just need to do it once):
As noted with the releases, in Alpha stage there is no update path provided yet, so such doing things manually becomes necessary from time to time.
(If this fixes the issue for you, please set to "Closed (works as designed)".)
Comment #12
christianadamski commentedCache has been rebuild with later versions already, including the latest. So I can't test this anymore.
Assume this fixed.
Comment #13
borisson_Awesome, thanks for confirming @ChristianAdamski. Closing this issue.
Comment #14
geerlingguy commentedI can confirm this (#11) fixed the issue on a site running alpha14 (and not yet upgraded to a later version). Thanks for posting the fix!