{"action":"closed","issue":{"url":"https://api.github.com/repos/garaio/xapian_db/issues/44","labels_url":"https://api.github.com/repos/garaio/xapian_db/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/garaio/xapian_db/issues/44/comments","events_url":"https://api.github.com/repos/garaio/xapian_db/issues/44/events","html_url":"https://github.com/garaio/xapian_db/issues/44","id":27835616,"number":44,"title":"sidekiq_queue config is not honored","user":{"login":"halfbyte","id":299,"avatar_url":"https://avatars.githubusercontent.com/u/299?v=3","gravatar_id":"","url":"https://api.github.com/users/halfbyte","html_url":"https://github.com/halfbyte","followers_url":"https://api.github.com/users/halfbyte/followers","following_url":"https://api.github.com/users/halfbyte/following{/other_user}","gists_url":"https://api.github.com/users/halfbyte/gists{/gist_id}","starred_url":"https://api.github.com/users/halfbyte/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/halfbyte/subscriptions","organizations_url":"https://api.github.com/users/halfbyte/orgs","repos_url":"https://api.github.com/users/halfbyte/repos","events_url":"https://api.github.com/users/halfbyte/events{/privacy}","received_events_url":"https://api.github.com/users/halfbyte/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2014-02-18T22:50:13Z","updated_at":"2015-12-04T06:30:17Z","closed_at":"2015-12-04T06:30:17Z","body":"I've just noticed that even though the docs say that SidekiqWriter uses 'xapian_db' as the default queue, and even though you should be able to ovewrite the used queue by configuring it with sidekiq_queue: in the yml file, these settings are not honored and all index updates are queued in \"default\". \r\n\r\nThe change to correct the behaviour would be relatively trivial, just adding one line to sidekiq_writer.rb should do the trick:\r\n\r\n```ruby\r\n      SidekiqWorker.class_eval do\r\n        include Sidekiq::Worker\r\n        sidekiq_options :queue => XapianDb::Config.sidekiq_queue ## THIS LINE ADDED\r\n      end\r\n```\r\n\r\nThe reason why I'm not instantly sending a pull request is because I have two questions I would like to have answered from someone before I feel confident to do that:\r\n\r\n1. This would probably, without additional changes, break people's installations. If you use additional queues in Sidekiq, you have to configure them explicitly, otherwise they are ignored by the worker process. One solution to this would be to change the \"standard\" queue for Sidekiq in both code and docs to \"default\". \r\n\r\n2. While the above change works for me so far, I am not sure if using XapianDB::Config in this manner is particularly safe. I would love to get some feedback from you on this. If it is, fine, if it is not, one solution would be to require a more recent version of sidekiq which has \"enqueue_in\" methods which would allow us to choose the queue during runtime and not on initialisation.\r\n\r\nPlease let me know what you think and I'll send a pull request asap.\r\n\r\n\r\n\r\n"}}