DJ delta indexing: Can I avoid delta indexing for non searchindex relevant model attribute changes?
I have a user model that has a last_active attribute that is constantly updated when a user is logged in. Any such update causes sphinx to create delta indexing dj jobs, although no fields relevant for the serach are updated. How can I avoid this?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Pat Allan on Aug 18, 2011 @ 01:39 AM
Hi Nico
The following (or something similar) should do the trick:
The
false
flag tells TS to not run a delta index request after the block is complete (it defaults totrue
).2 Posted by Nico on Aug 18, 2011 @ 06:10 AM
Thanks, I give it a shot.
3 Posted by Nico on Aug 18, 2011 @ 06:43 AM
Just wondering if thinking sphinx could figure out automatically if relevant fields have changed on a save and then conditionally trigger the (delayed) delta indexing?
Support Staff 4 Posted by Pat Allan on Aug 18, 2011 @ 06:49 AM
It does try to - but if you're using associations or SQL snippets in fields and attributes, it can't be sure, so it works with the assumption that it's better to fire a delta request.
5 Posted by Nico Ritsche on Aug 18, 2011 @ 07:11 AM
Ah, okay, sounds reasonable.
Thanks for making sphinx available on Heroku by the way. Great job! ;-)
Support Staff 6 Posted by Pat Allan on Aug 18, 2011 @ 07:14 AM
Thanks :)
Pat Allan closed this discussion on Aug 18, 2011 @ 07:14 AM.