ok,
i think i have a misconception somewhere and would VERY appreciate if
someone would be able to clarify that.

i killed the 'searchd' process manually and restarted it with
ts:start.

i invoked manually 'indexer -c path/to/conf --rotate'

and not it appears that deltas ARE showing on results, but only after
couple of moments after the actual record is created.

My questions are:

1. is this delay normal?
2. i don't want to manually kill searchd everytime... so i'm pretty
sure the problem is somewhere on my deployment process... can someone
point me to the must updated tutorial (until the homepage will be
finished that is.)



On May 21, 7:21 pm, Pat Allan <[email protected]> wrote:
> Hm, wait, just re-thinking - if you can't see the output from script/
> console, then it's not a path issue - because script/console is run by  
> yourself, not passenger.
>
> What's the output of `indexer` (with angle quotes) in script/console?
>
> --
> Pat
>
> On 21/05/2009, at 1:25 PM, Elad Meidar wrote:
>
>
>
> > it makes no difference....
>
> > still i can't see no sphinx messages when new items are created, and
> > delta => true status_updates aren't in results either...
>
> > is there anything else i need to do in order to enable access to the
> > indexer bin ? maybe permissions to the www user? seem like this is the
> > problem.
>
> > On May 21, 3:46 pm, Pat Allan <[email protected]> wrote:
> >> You probably don't need bin_path set on your development  
> >> environment -
> >> I've never had problems, because it's all run by my own user, not
> >> passenger.
>
> >> And it's not something that appears in the configuration file, it's
> >> just how Thinking Sphinx makes calls to the binaries.
>
> >> Cheers
>
> >> --
> >> Pat
>
> >> On 21/05/2009, at 12:43 PM, Elad Meidar wrote:
>
> >>> you nailed it.
>
> >>> on development it's working...
>
> >>> but i don't seem to see the bin_path instructions on the development
> >>> conf.... where it should be ?
> >>> this is my sphinx.yml
>
> >>> development: &my_settings
> >>> min_prefix_len: 0
> >>> min_infix_len: 1
> >>> min_word_len: 1
> >>> max_results: 70000
> >>> bin_path: /usr/local/bin
> >>> morphology: none
> >>> charset_table: ** huge charset.. i removed it for readability **
> >>> test:
> >>> <<: *my_settings
> >>> production:
> >>> <<: *my_settings
>
> >>> On May 21, 3:18 pm, Pat Allan <[email protected]> wrote:
> >>>> Ah, if you're not seeing any output, then it could be that the  
> >>>> Sphinx
> >>>> binaries - indexer and searchd - aren't referenced in the PATH set
> >>>> within your web server (I'm guessing passenger).
>
> >>>> You'll need to add the following to your config/sphinx.yml (or  
> >>>> create
> >>>> it):
>
> >>>> production:
> >>>> bin_path: /usr/local/bin
>
> >>>> The bin_path should be set to the output of `which indexer` from  
> >>>> the
> >>>> shell - minus /indexer, of course.
>
> >>>> You're not seeing the problem with the datetime approach because
> >>>> you're invoking the rake task yourself, not via the web server.
>
> >>>> ... of course, I may be completely wrong about the problem :)
>
> >>>> --
> >>>> Pat
>
> >>>> On 21/05/2009, at 12:08 PM, Elad Meidar wrote:
>
> >>>>> Hi guys,
>
> >>>>> I tried to wrestle with it a little bit, tried to create a new
> >>>>> StatusUpdate record to see what the log says... but nothing there,
> >>>>> no
> >>>>> sphinx message of any kind.
> >>>>> I decided to change my model to use set_property :delta  
> >>>>> => :datetime
> >>>>> instead of :delta => true and it appears to be working at the
> >>>>> moment... but i would still like to find out why the :delta =>  
> >>>>> true
> >>>>> fails.
>
> >>>>> i attach my production.conf so you might be able to point out  
> >>>>> where
> >>>>> i'm wrong (generated with ts:conf only).
> >>>>>http://pastie.org/485658
>
> >>>>> Thanx guys..
>
> >>>>> Scott.. yeah, it's not an extortion of course... at least not as
> >>>>> worst
> >>>>> as it used to be :)
>
> >>>>> On May 21, 2:44 pm, Pat Allan <[email protected]> wrote:
> >>>>>> Hi Elad
>
> >>>>>> The ts:in:delta task is only for datetime deltas, and you're  
> >>>>>> using
> >>>>>> the
> >>>>>> default approach instead, so you don't need to run that.
>
> >>>>>> When you create a new status update in console, do you also see
> >>>>>> several lines from the Sphinx indexer task being output?
>
> >>>>>> --
> >>>>>> Pat
>
> >>>>>> On 21/05/2009, at 7:52 AM, Elad Meidar wrote:
>
> >>>>>>> i have sphinx 0.9.8.1 installed and for some reason, it  
> >>>>>>> refuses to
> >>>>>>> take deltas into consideration when searching, until i re-index
>
> >>>>>>> here is an example for the console:
>
> >>>>>>> #<StatusUpdate id: 31109, content: "Microsoft just patented
> >>>>>>> extortion", author: "xxxx", source_id: "1", direct_link:  
> >>>>>>> "hxxxx",
> >>>>>>> uid:
> >>>>>>> "234234233", created_at: "2009-05-21 14:14:55", updated_at:
> >>>>>>> "2009-05-21 14:14:55", handler: "t", posted_at: "1242915290",
> >>>>>>> delta:
> >>>>>>> true>
>
> >>>>>>> but searching for "microsoft":
>
> >>>>>>> StatusUpdate.search("@content microsoft", :per_page =>
> >>>>>>> 1000, :match_mode => :extended)
>
> >>>>>>> does not return this result.
>
> >>>>>>> here is my index:
>
> >>>>>>> define_index do
> >>>>>>> indexes content, :sortable => true
> >>>>>>> has posted_at, handler, author
>
> >>>>>>> has users(:id), :as => :user_ids
> >>>>>>> set_property :delta => true # for stuff that are added between
> >>>>>>> indexing
> >>>>>>> end
>
> >>>>>>> another thing is that when i 'ts:in:delta', nothing seem to be
> >>>>>>> happening, the delta flag stays as it should on new records, but
> >>>>>>> they
> >>>>>>> still don't appear in search (actually the rake task does not  
> >>>>>>> even
> >>>>>>> return any output).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" 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/thinking-sphinx?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to