I found this new response which says the error below.
heroku run rake fs:index
Running rake fs:index attached to terminal... up, run.1
Starting Index Request
end of file reached
Tasks: TOP => fs:index
Also when I check the heroku logs from my application it says
2012-06-18T18:09:32+00:00 heroku[run.1]: Awaiting client
2012-06-18T18:09:32+00:00 heroku[run.1]: Starting process with
command bundle exec rake fs:index
2012-06-18T18:09:32+00:00 heroku[run.1]: State changed from
starting to up
2012-06-18T18:10:08+00:00 heroku[run.1]: Process exited with status
2012-06-18T18:10:08+00:00 heroku[run.1]: State changed from up to
Please check and let me know if I have to change any
configuration in my application.
Pat Allan on 18 Jun, 2012 07:26 PM
How are you using the user_id field in each index? I'd recommend switching that to an attribute instead (which are always sortable), and can be integers natively in Sphinx - this should avoid the type issues.
user_id is an attribute of the object wherever I have defined
index and I'm using that attribute for extended match mode in my
search methods, and I read in the documentation that integer
datatypes are supported by flying sphinx and sortable too just like
thinking sphinx. Can I know why is it not getting indexed and
throwing the exception below ?
indexing index 'matching_core'...
ERROR: index 'matching_core': sql_range_query: ERROR: invalid input
syntax for integer: ""
If I cannot index user_id which is a attribute of the class, is
there any other recommendations you suggest ? I need to use that
user_id attribute for my search extended match modes.
In Thinking Sphinx's index definitions, the 'indexes' method is for fields, the 'has' method is for attributes. If you're sorting by user_id, then it may be best to have it as an attribute, but that really depends on how else you're using it (can you show me the search calls?)
That said, if you need user_id to be treated as a string, then your best option is to cast it as one:
What I'm trying to do with is I need to fetch all the rows which
has the input value in fields and either the user_id must be the
current user or the permission should be public. Extended match
mode is one way I found for doing this.
Since I'm using user_id for checking in the extended match mode,
I had to index that for searching.
Pat Allan on 19 Jun, 2012 12:25 PM
Great to hear it's working.
As for deltas, I'm afraid it's not something I'll be adding to the wooden plan - from a resource perspective, it's just not feasible to have the increase in demand on those servers and keep everything reliable.
I have an application(gamezone-next-dev.herokuapp.com) running on heroku. I ahve added flyings-phinx for searching. There is an issue i am facing with it. When i run rake fs:index, it just works fine and all of articles gets indexed.
But whenever an article is created, it doesn't get indexed and says: 'sh: indexer not found'
Can you please find what is the isuue