I have my app working with Sunspot Solr locally, supporting unicode
with no issues. In production however, with Heroku and Websolr, all
unicode queries return zero results. I have confirmed with Websolr
support I can query directly against their Solr system with unicode
and it works fine. When I query from my production app however, they
saw something like this in the log: q=أرسنا
So it doesn't seem to be related to Websolr. I also tried running the
local app in production mode (pointing to Websolr), and once I do
that, queries return no results again!
I'm wondering if anyone had faced similar problem, and where should I
be looking for answers? I tried to set solr production log level to
INFO or more to see what's being sent to Solr, but for some reason
that's not showing in the server log as well.
I saw this one come up again recently. Basically, RSolr isn't setting the charset in its POST request body, causing Tomcat to interpret it as ISO-8859-1, resulting in the mangling that you see. There is a fix in RSolr here which should go out in the next release:
> I have my app working with Sunspot Solr locally, supporting unicode > with no issues. In production however, with Heroku and Websolr, all > unicode queries return zero results. I have confirmed with Websolr > support I can query directly against their Solr system with unicode > and it works fine. When I query from my production app however, they > saw something like this in the log: q=أرسنا
> So it doesn't seem to be related to Websolr. I also tried running the > local app in production mode (pointing to Websolr), and once I do > that, queries return no results again!
> I'm wondering if anyone had faced similar problem, and where should I > be looking for answers? I tried to set solr production log level to > INFO or more to see what's being sent to Solr, but for some reason > that's not showing in the server log as well.
> Thanks
> -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en.
> I saw this one come up again recently. Basically, RSolr isn't setting the
> charset in its POST request body, causing Tomcat to interpret it as
> ISO-8859-1, resulting in the mangling that you see. There is a fix in RSolr
> here which should go out in the next release:
> In the mean time, you can use the RSolr git repo directly in your Gemfile
> to get that fix today.
> On Thu, Jan 5, 2012 at 7:01 AM, Bashar Abdullah
> <bashar.abdul...@gmail.com>wrote:
> > Hi,
> > I have my app working with Sunspot Solr locally, supporting unicode
> > with no issues. In production however, with Heroku and Websolr, all
> > unicode queries return zero results. I have confirmed with Websolr
> > support I can query directly against their Solr system with unicode
> > and it works fine. When I query from my production app however, they
> > saw something like this in the log: q=أرسنا
> > So it doesn't seem to be related to Websolr. I also tried running the
> > local app in production mode (pointing to Websolr), and once I do
> > that, queries return no results again!
> > I'm wondering if anyone had faced similar problem, and where should I
> > be looking for answers? I tried to set solr production log level to
> > INFO or more to see what's being sent to Solr, but for some reason
> > that's not showing in the server log as well.
> > Thanks
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Heroku" group.
> > To post to this group, send email to heroku@googlegroups.com.
> > To unsubscribe from this group, send email to
> > heroku+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/heroku?hl=en.
