Hi Pat, Thanks for that, you're spot on. I upgraded recently to delayed job 3.0.3, ts-dalayed-delta 1.1.3 and thinking-sphinx 2.0.12. I realized I have another server instance publishing tasks to the delayed_jobs table that hadn't been upgraded. It was still using 'indexes'.
Cheers, Adam Boas On 28/08/2012, at 9:12 PM, Pat Allan <[email protected]> wrote: > Hi Adam > > Have you updated versions of Thinking Sphinx and/or Riddle lately? A while > ago, I switched syntax from indexes to indices in both libraries (and > ts-delayed-delta) - what versions of all three gems are you using? > > -- > Pat > > On 28/08/2012, at 7:42 AM, Adam Boas wrote: > >> Its strange 'index".pluralize returns "indices" but that is not what I am >> seeing in the delayed job handler >> >> >> Adam Boas >> >> >> >> >> On 28/08/2012, at 3:24 PM, Simon Russell <[email protected]> wrote: >> >>> Does adding a custom inflection help? (I'm assuming that >>> "index".pluralize isn't returning the right thing...) >>> >>> On Tue, Aug 28, 2012 at 3:11 PM, Adam Boas <[email protected]> wrote: >>>> Hi All, >>>> >>>> I know there is a fair bit of Thinking Sphinx wisdom in this group and I >>>> was hoping to get some help on an inflection issue I am seeing using >>>> Thinking Sphinx Delayed Delta. >>>> >>>> What is happening is that when a Product in our system goes out of stock a >>>> delayed job task is written with the following: >>>> >>>> --- !ruby/object:ThinkingSphinx::Deltas::FlagAsDeletedJob >>>> document_id: 80380 >>>> indexes: >>>> - product_core >>>> >>>> That YAML is deserialized with an array called indexes. >>>> ThinkingSphinx::Deltas::FlagAsDeletedJob unfortunately is looking for >>>> indices, the long and the short of which is that it results in: >>>> >>>> NoMethodError: undefined method `each' for nil:NilClass >>>> >>>> when the flagAsDeletedJob starts to iterate through the indices. >>>> >>>> Anyone have any ideas how I can either get the indexes to serialize as >>>> indices or vice-versa >>>> >>>> Cheers, >>>> >>>> Adam Boas >>>> >>>> >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Ruby or Rails Oceania" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/rails-oceania?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Ruby or Rails Oceania" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/rails-oceania?hl=en. >>> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
