: The top of the stack was the stack I posted.  I am not able to give the
: entire stack, but this is the important part.  The exception is something
: about searching with null.

when i say "the top of the stack trace" i mean what you just described:
"something about searching with null" .. what exactly does it say about
searching with null?  What is the class of the exception?

This is an example of the "top" of a stack trace...

org.apache.solr.core.SolrException: Error parsing Lucene query
        at org.apache.solr.search.QueryParsing.parseQuery(QueryParsing.java:87)
        at 
org.apache.solr.request.StandardRequestHandler.handleRequest(StandardRequestHandler.java:108)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:586)
        ...

equally important is if the stack trace contains any lines starting
with someling like "Caused by:" which would be much "lower" in the stack,
possibly after your own custom classes, but they show the root of the
problem.  the example Solr exception i posted above is fairly useless for
understanding the root cause of the problem unless you look at the full
stack trace and see much farther down a "Caused by" line explaining what
really went wrong...

org.apache.solr.core.SolrException: Error parsing Lucene query
        at org.apache.solr.search.QueryParsing.parseQuery(QueryParsing.java:87)
        at 
org.apache.solr.request.StandardRequestHandler.handleRequest(StandardRequestHandler.java:108)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:586)
        at org.apache.solr.servlet.SolrServlet.doGet(SolrServlet.java:91)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
        ...
Caused by: org.apache.lucene.queryParser.ParseException: Cannot parse 'id:*1*': 
Lexical error at line 1, column 4.  Encountered: "*" (42), after : ""
        at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:129)
        at org.apache.solr.search.QueryParsing.parseQuery(QueryParsing.java:77)
        ...


...these are just a few example why only posting "part" of a stack trace
isn't allways enough to help diagnose your problem.




-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to