Closed (fixed)
Project:
Search API Grouping
Version:
7.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Oct 2013 at 22:56 UTC
Updated:
16 Feb 2014 at 12:40 UTC
Jump to comment: Most recent
Comments
Comment #1
das-peter commentedThat was my idea too. However, I couldn't find the time to work on this. Would be absolutely great if you could figure out how to put that into a batch :)
Comment #2
malks commentedHi das-peter,
I ended up not using your module, but
stoleadapted many of the features from it as I needed most of the funtionality but also needed to extend it for our specific use case. Having said that I did end up having to work out how to batch the trackItemChange and I'm pretty sure I could retrofit into your module. Is this something you would like done still? How do I go about it? i.e. fork and pull against your dev repo?Thanks,
Anthony.
Comment #3
das-peter commentedAbsolutely :)
Whatever you'd prefer and produces a patch that can be applied to the module ;)
As I don't know the code I can't tell you if it can be done using git or if you've to do it manually.
Comment #4
das-peter commentedI've just committed an enhancement for the whole re-index / clear index methods.
The generation of the permutations is now done using the queue and cron. Further I've replaced
entity_load()wherever possible by Entity Field Query which hopefully drastically reduces the required processing & memory consumption.There are also new / adjusted drush commands:
sapi-gpqwill process the items in the permutation queue.sapi-gguses the permutation queue now. If you abort it's execution you should be able to continue the processing later withsapi-gpq- or cron will do it for you.For now I didn't adjust the method
trackItemChange(). Let's see if this method really becomes such and amount of entities to process that we need to use an extra queue.