Loggly Solr Error

[jimpo]

Some sort of Solr error showing up on Loggly a lot. You know what this is @jodoglevy ? Sorry about GitHub's formatting.

Error: <title>Apache Tomcat/6.0.28 - Error report</title><style></style>

HTTP Status 400 - org.apache.lucene.queryParser.ParseException: Cannot parse ':"undefined"': Encountered " ":" ": "" at line 1, column 0.
Was expecting one of:
<NOT> ...
"+" ...
"-" ...
"(" ...
"" ...
<QUOTED> ...
<TERM> ...
<PREFIXTERM> ...
<WILDTERM> ...
"[" ...
"{" ...
<NUMBER> ...
<TERM> ...
"" ...

---

type Status report

message org.apache.lucene.queryParser.ParseException: Cannot parse ':"undefined"': Encountered " ":" ": "" at line 1, column 0.
Was expecting one of:
<NOT> ...
"+" ...
"-" ...
"(" ...
"" ...
<QUOTED> ...
<TERM> ...
<PREFIXTERM> ...
<WILDTERM> ...
"[" ...
"{" ...
<NUMBER> ...
<TERM> ...
"" ...

description The request sent by the client was syntactically incorrect (org.apache.lucene.queryParser.ParseException: Cannot parse ':"undefined"': Encountered " ":" ": "" at line 1, column 0.
Was expecting one of:
<NOT> ...
"+" ...
"-" ...
"(" ...
"" ...
<QUOTED> ...
<TERM> ...
<PREFIXTERM> ...
<WILDTERM> ...
"[" ...
"{" ...
<NUMBER> ...
<TERM> ...
"" ...
).

---

Apache Tomcat/6.0.28

at IncomingMessage. (/app/node_modules/solr/lib/solr.js:35:19)
at IncomingMessage.emit (events.js:88:20)
at HTTPParser.parserOnMessageComplete as onMessageComplete
at Socket.socketOnData as ondata
at TCP.onread (net.js:374:27)

[jodoglevy]

@jep37 the important part of the error is Cannot parse ':"undefined"'. Because solr uses the syntax of title:"a title goes here", field:value, I assume :"undefined" means the query is missing a field to search on (ie title) and the value it is searching on is undefined, which we are manually wrapping in quotes. What confuses me is that search seems to be working on the site...

[jodoglevy]

@jep37 are you still getting this a lot?