The problem was gone. Thank you very much for the handling.
Koji
Ryan McKinley wrote:
sorry. I tested with something that did not duplicate the problem.
update and try rev 536048.
Koji Sekiguchi wrote:
Ryan,
Thank you for committing SOLR-214, but we are still facing the
garbled character
sorry. I tested with something that did not duplicate the problem.
update and try rev 536048.
Koji Sekiguchi wrote:
Ryan,
Thank you for committing SOLR-214, but we are still facing the garbled
characters problem
under Tomcat 5.5.23.
I checked the patch, but unfortunately, ContentStreamBas
Ryan,
Thank you for committing SOLR-214, but we are still facing the garbled
characters problem
under Tomcat 5.5.23.
I checked the patch, but unfortunately, ContentStreamBase.getReader()
works correctly
when using stream.* parameters. Without stream.* parameters, contentType
is null and
Con
I also have a real world document that doesn't work (from our nutch crawls):
wget http://variogr.am/badfile.txt
./post.sh badfile.txt
A solr rock star advised me to try SOLR-214, which fixes the
problem. Perhaps he'll illuminate us as to the reasons! But for now
be careful with Resin.
I d
I also have a real world document that doesn't work (from our nutch
crawls):
wget http://variogr.am/badfile.txt
./post.sh badfile.txt
A solr rock star advised me to try SOLR-214, which fixes the problem.
Perhaps he'll illuminate us as to the reasons! But for now be careful
with Resin.
On May 7, 2007, at 11:05 AM, Brian Whitman wrote:
Using resin 3.0.23 with a trunk solr war I am having a problem
adding documents with utf-8 characters, including the utf8-example
in exampledocs.
The document simply doesn't get added to Solr. Flat ascii documents
work fine as does all non-
