Pat Allan on 18 Jan, 2013 12:04 AM
I've been using it over a month now with TS v3 on a production
site (66k delta requests), and it works fine. You'll need to use
the sidekiq branch of my ts-resque-delta fork though (the original
ts-sidekiq-delta was forked from ts-resque-delta, hence Github got
a bit confused with the naming):
I finally got time to transition to Sidekiq.
One question is:
So this is a branch of ResqueDelta.
In my delta arguement what should I use: FlyingSphinx::ResqueDelta or is there a: FlyingSphinx::SidekiqDelta or should I use: ThinkingSphinx::Deltas::SidekiqDelta
Im moving from DelayedDelta. So this is a bit new to me.
Using sidekq 2.8.0 it work perfectly in local development but not
at all for flying sphinx. It just contacts the flying sphinx server
from the web server thread not running the sidekiq worker at all.
It's like iits not being enqueued at all.
Perhaps it makes sense to tell you what my plan is - I wish we
could move away from delayed_job completely, so for now I am using
sidekiq for everything else like images processing and emails. I
wish I could drop this last worker of delayed_job that we use
for getting the delta indexes.
So after this small introduction here is the code, gem file and
issue that keeps poping up:
indexes store(:name), :as => :store_name, :sortable => true
indexes brand(:name), :as => :brand_name, :sortable => true
indexes category(:name), :as => :category_name, :sortable => true
indexes tags.name, :as => :tags
has "RADIANS(stores.latitude)", :as => :latitude, :type => :float
has "RADIANS(stores.longitude)", :as => :longitude, :type => :float
group_by 'stores.latitude', 'stores.longitude'
if Rails.env.production? || Rails.env.staging?
set_property :delta => ThinkingSphinx::Deltas::SidekiqDelta
I have 'ThinkingSphinx::Configuration::Defaults::PANES <<
' setup inside the initializer but I don't think this has anything
to do with it as if I understood documentation this pane gets
auto-injected when 'geo' attribute is passed in.
Please let me know what am I missing, all hints are always
Pat Allan on 11 Apr, 2013 02:49 PM
The issue here is that SphinxQL just requires geodist, not @geodist - it's no longer a special attribute, but a generated one. If you remove the @ (and if you like, change it to the symbol (e.g.: :geodist) when using it in a filter), it should work fine.
I have begun to get these warnings: 2013-04-25T16:36:34Z 5300 TID-ovs5uycmo WARN:
ThinkingSphinx::Deltas::SidekiqDelta::DeltaJob - :timeout is unsafe
and support has been removed from Sidekiq, see http://bit.ly/OtYpK
for details 2013-04-25T16:36:34Z 5300 TID-ovs5uycmo WARN:
ThinkingSphinx::Deltas::SidekiqDelta::FlagAsDeletedJob - :timeout
is unsafe and support has been removed from Sidekiq, see
http://bit.ly/OtYpK for details Hmmm...
This is probably just a problem with sidekiq deltas but I cannot
report an issue on a branch.