Upgrade from Rails 3.2, sunspot_rails and sunspot_solr 1.3.3, to Rails 4.x and gems version 2.1.x

[clod81]

Hi,
I'm trying to upgrade my Rails app to rails v 4.x and therefore using gems v > 2.x .
I tried to use gems version 1.3.3, but it looks like they are not compatible with new rails version...

I now start solr in development and test doing: sunspot-solr start , leaving default options.

Anyway, I have most of the things working, apart from a strange behavior.

I have a model defined pretty much like this:

class AAA < ActiveRecord::Base

searchable do
    text    :code
    text    :name
end

end

Let's say I have a database entry with those values:

code: 'ABC'
name 'testy searchy'

If I try to do:

AAA.search do
   fulltext('abc')
end

I get proper result

If I try to do:

AAA.search do
   fulltext('ab')
end

I get proper result

If I try to do:

AAA.search do
   fulltext('testy')
end

I get proper result.

But if I try:

AAA.search do
   fulltext('tes')
end

I don't get any results, whereas in version 1.3.3 everything used to work fine.

What am I missing?

[clod81]

I tried on an total empty / brand new rails 4 project, with just 1 active record model, 2 string fields.
I have the exact same issue described above.

[clod81]

I ended up patching 1-3-stable to work with ralis 4 (only)

https://github.com/clod81/sunspot/tree/1-3-rails4

unsure if changes are all 'perfect', but seems to be working nicely with my app

[coderdave]

What's the status on this being fixed? I have the same issue.

[clod81]

if you're interested, my branch in my fork https://github.com/clod81/sunspot/tree/1-3-rails41 works ok on rails 4.1. it's not a proper fix, but I never had issues so far and works as previously

[coderdave]

That's cool that there's a fork that works, but when you're experimenting with a library for the first time that doesn't even work as expected with the most basic setup, it's very discouraging. :(

[mlh758]

Closing this due to age and this doesn't appear to still be an issue.