So, the CSV-update fails. I have no idea whats wrong with that file, but it shouts, that there is something wrong encapsuled. It seems to be the same mistake as it is mentioned here: http://markmail.org/message/lo3vztzezyuc6h3w#query:solr%20csv%20invalid%20char%20between%20encapsulated%20token%20end%20delimiter+page:1+mid:lo3vztzezyuc6h3w+state:results
However, this don't help and is stuff for another topic - I only mention that, because I have said I will try it. Beeing busy and confused yesterday, I have copied old schema.xml-information to you..., sorry. I should drink some more coffee, right? There is one modification to the xml-schema. It's a custom filter, a special variant of the stopword-filter. This filter cuts the input-phrases in a special way. That means, whenever a stopword occurs, it deletes words related to the stopword as well. Since I have had outcommented this filter, the search works like one can expect it without my custom filter. I know that some of you do some consulting for lucene/solr. Did you ever see such an error? I mean, I don't know much about the architecture of lucene/solr and I am absolutely unable to reproduce the error on my own, since I don't know where to start. The only thing I have got is that nothing after the 55th row is searchable. Furthermore: if I change my sql-statement to something like WHERE ID between 56 AND 100, ONLY the 56th line is searchable. Thank you very much! Mitch -- View this message in context: http://n3.nabble.com/Absolutely-empty-resultset-regardless-of-what-I-am-searching-for-tp683866p685697.html Sent from the Solr - User mailing list archive at Nabble.com.
