Settings take locally, but not on Heroku with Bonsai - again

[iterion]

Model/Mapping I'm having trouble with:

  include Tire::Model::Search
  include Tire::Model::Callbacks
  index_name BONSAI_INDEX_NAME

  #elasticsearch mapping -------
  settings :analysis => {
            :filter => {
              :name_ngram  => {
                "type"     => "nGram",
                "max_gram" => 8,
                "min_gram" => 2 }
              },
              :analyzer => {
                :name_analyzer => {
                  "tokenizer"    => "standard",
                  "filter"       => ["lowercase", "stop", "name_ngram"],
                  "type"         => "custom"
                }
              }
            } do
      mapping do
        indexes :id, type: 'integer'
        indexes :name, analyzer: 'name_analyzer'
        indexes :other_names, analyzer: 'name_analyzer'
        indexes :city
        indexes :state
        indexes :domain
      end
  end

  # def to_indexed_json
  #   to_json(methods: [:name])
  # end

  class << self
    def search(params)
      tire.search(page: params[:page], per_page: per_page, load: true) do
        query do
          boolean do
            if params[:query].present?
              must { term :other_names, params[:query] }
            end
          end
        end
      end
    end
  end

Also, I have set up an initializer at config/initializers/bonsai.rb as recommended and ran the below steps, all to no avail:

      1)  drop out `to_indexed_json` from your University model ( at the opposit of README indication )
      2)  remove & add back Bonsai.io/Heroku add-on ( this will remove your index on Heroku, be careful ! )
      3)  reindex ElasticSearch by running `heroku run:detached rake environment tire:import CLASS='University'`
           ( Heroku will bill this extra "run" process so know what you're doing )

I'm running:
rails (3.2.5)
tire (0.4.2)

Let me know if more detail is needed.

[iterion]

Exploring the console on heroku - I found this:

irb(main):009:0> index.settings
NoMethodError: undefined method `[]' for nil:NilClass
    from /app/vendor/bundle/ruby/1.9.1/gems/tire-0.4.2/lib/tire/index.rb:62:in `settings'
    from (irb):9
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.5/lib/rails/commands/console.rb:47:in `start'
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.5/lib/rails/commands/console.rb:8:in `start'
    from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.2.5/lib/rails/commands.rb:41:in `<top (required)>'
    from script/rails:6:in `require'
    from script/rails:6:in `<main>'
irb(main):010:0> index.response
=> 200 : {"[bonsai_index_name]-[large_integer]":{"settings":{"index.number_of_replicas":"1","index.number_of_shards":"1"}}}

The error obviously comes from setting the index name based on the ENV variable as the index name in the response does not match. Might this be preventing us from saving the mapping too?

Also, this:

irb(main):021:0> index.create
=> false
irb(main):022:0> index.response
=> 401 : {"error": "Not authorized: Some endpoints are admin-only, ask support@onemorecloud.com."}

--edit-- More Info:

If I modify the name of the index like so:

index.instance_variable_set :@name, "#{index.name}-[large_int_that_was_returned]/university"

I can then run:

index.delete
 => true

[zacksiri]

This could be related to my issue although mine is having issues with callbacks not get request, I can run tire import but it seems if I update create or delete it doesn't work.

[zacksiri]

Btw interesting that I am also on 3.2.5 and tire 0.4.2 perhaps there is something not right with this combo?

[iterion]

@zacksiri take a look at https://saas.found.no/

Their support actually gets back to me, unlike bonsai.

[zacksiri]

hey, yea i am thinking of switching too been having too many issues with bonsai

[karmi]

@iterion Sorry for not getting back to you here... these problems with Bonsai are piling up... will have to find some time to investigate it.

[iterion]

@karmi no worries, things are working quite well for me with Found

Most of the issues I saw with Bonsai came from restrictions on their end.

[karmi]

@iterion Should we close this, then? I'm afraid I still can't see anything wrong in the setup...

[iterion]

@karmi Yeah, migrating to a different provider fixed the issue, so it appears tire is fine.

[karmi]

@iterion Cool.

[nz]

For posterity: this issue was addressed in Bonsai a couple months ago, back in October 2012. We've also since launched to production in January 2013 and generally work pretty smoothly with Tire's conventions these days.