Hi,
I have a situation where I have lots of users concurrently creating/
updating entries that I have indexed. I think I can get away with
just running ts:index once an hour or so to get relatively up to date
results. My issue is that users also have the option to lock entries,
at which point
Pat will be able to give a longer answer, but in the meantime..
Jason wrote:
1. Why do I need a delta column if I'm using delayed_jobs? I tried
to get rid of it, but TS complained loudly.
Even with delayed_job, the indexer needs to know which records belong in
the delta index. Since the
Pat,
I tried this on a set of a couple hundred records and it works well.
Thanks !
Are you going to summarize all the recent changes sometime? It looks
like there may have been some changes to work with MVA facets better
too ?
-Eric
On May 8, 2009, at 11:21 AM, Pat Allan wrote:
Hi
Simon,
The delta property is extensible so you could pass a class to do what you
desire (you could wrap a conditional around the delta operation).
See http://github.com/dpickett/workling_delta_indexer/tree/master for an
example of using a custom delta handler.
Regards,
Dan
On Thu, May 14, 2009
Hi Simon
If a locked entry is indicated by a boolean attribute in the index,
then you shouldn't even need delta indexes. Thinking Sphinx now
updates attributes on the fly, given the following:
* The attribute is an integer, timestamp or boolean
* The attribute is generated from a straight
