Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating to TS3 got some error #415

Closed
lephyrius opened this issue Jan 5, 2013 · 8 comments
Closed

Migrating to TS3 got some error #415

lephyrius opened this issue Jan 5, 2013 · 8 comments

Comments

@lephyrius
Copy link

undefined method `<<' for nil:NilClass
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/active_record/sql_source.rb:107:in `block in prepare_for_render'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/active_record/sql_source.rb:104:in `each'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/active_record/sql_source.rb:104:in `prepare_for_render'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/active_record/sql_source.rb:61:in `render'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration/index.rb:29:in `block in render'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration/index.rb:29:in `collect'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration/index.rb:29:in `render'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/core/index.rb:48:in `render'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration.rb:39:in `block in render'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration.rb:39:in `collect'
.rvm/gems/ruby-1.9.3-p327/gems/riddle-1.5.4/lib/riddle/configuration.rb:39:in `render'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/configuration.rb:81:in `render'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/configuration.rb:87:in `block in render_to_file'
.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/open-uri.rb:35:in `open'
.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/open-uri.rb:35:in `open'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/configuration.rb:87:in `render_to_file'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/rake_interface.rb:4:in `configure'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/rake_interface.rb:31:in `index'
.rvm/gems/ruby-1.9.3-p327/gems/thinking-sphinx-3.0.0/lib/thinking_sphinx/tasks.rb:9:in `block (2 levels) in <top (required)>'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:228:in `call'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:228:in `block in execute'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:223:in `each'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:223:in `execute'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:166:in `block in invoke_with_call_chain'
.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:159:in `invoke_with_call_chain'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:187:in `block in invoke_prerequisites'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:185:in `each'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:185:in `invoke_prerequisites'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:165:in `block in invoke_with_call_chain'
.rvm/rubies/ruby-1.9.3-p327/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:159:in `invoke_with_call_chain'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/task.rb:152:in `invoke'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:143:in `invoke_task'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:101:in `block (2 levels) in top_level'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:101:in `each'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:101:in `block in top_level'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:110:in `run_with_threads'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:95:in `top_level'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:73:in `block in run'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:160:in `standard_exception_handling'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/lib/rake/application.rb:70:in `run'
.rvm/gems/ruby-1.9.3-p327/gems/rake-10.0.3/bin/rake:33:in `<top (required)>'
.rvm/gems/ruby-1.9.3-p327/bin/rake:23:in `load'
.rvm/gems/ruby-1.9.3-p327/bin/rake:23:in `<main>'
Tasks: TOP => ts:rebuild => ts:index

Got this error when migrating to thinking sphinx 3.

@pat
Copy link
Owner

pat commented Jan 5, 2013

What are your index definitions?

@pat
Copy link
Owner

pat commented Jan 5, 2013

Another thought for this issue: it looks like you're manually specifying a type for an attribute, but these have changed slightly with TS v3. :datetime has become :timestamp (matching Sphinx's own labelling), and :multi is now a separate setting, as there can be multi-value attributes of different types (:integer and :bigint). Here's an example of how the latter would change between TS versions:

has "CUSTOM SQL", :as => :values, :type => :multi
# becomes
has "CUSTOM SQL", :as => :values, :type => :integer, :multi => true

@lephyrius
Copy link
Author

Works with :datetime .

So now the only error I get is:

undefined method `excerpts' for #<Game:0x00000101ac2f68>

So is there any special way of handling excerpts in ThinkingSphinx 3 ?

@lephyrius
Copy link
Author

Ahh! Sorry now I see. A much nicer way of doing excerpts.

@lephyrius
Copy link
Author

Hmmm... Looks like I do need to call the excerpts function to get excerpts? I don't get excerpts from just the attribute.
Oh! Now im stupid. I needed the excerpts pane. :)

@pat
Copy link
Owner

pat commented Jan 5, 2013

@lephyrius did you get excerpts figured out?

@lephyrius
Copy link
Author

@pat Yes, thats why I closed this issue.

@pat
Copy link
Owner

pat commented Jan 10, 2013

I was just wondering what the cause of the issue was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants