Solr cannot parse EOF "\"

2,088 views
Skip to first unread message

Jennifer Eustis

unread,
Feb 11, 2016, 9:18:18 AM2/11/16
to islandora
Hi folks,

I've been seeing more errors of the type SolrCore cannot parse 'mods_subject_geographic_ms:"Central Street': Lexical error at line ..., column .... Encountered <EOF> after : "\"Central Street"

In looking into this, it appears that there are characters that need to be escaped and that aren't. One of the developers mentioned that someone is loading bad data. I'm not sure exactly what the errors means or how to go about solving this ... and sorry if this is a silly question from a nonprogrammer. Is there a way to address this issue such as changing the Solr settings in our site?

Thanks in advance for the help.

Jennifer

Diego Pino

unread,
Feb 11, 2016, 1:57:33 PM2/11/16
to islandora
Hi Jennifer, i see a mix of different quotes there (" and '). Are those queries coming from user input using a search form? Or from some module? Maybe just someone playing with advanced search? I'm not sure if we are escaping characters (enough?) in the search forms. Will try here.

best!

Diego

Jennifer Eustis

unread,
Feb 11, 2016, 2:48:19 PM2/11/16
to islandora
Hi Diego,

I'm seeing this in the solr/#/logging - I get there by going to a browser and typing in the url for our fedora:8080/solr/#/logging. Right now, I'm unable to match these to records as I don't have enough information in the logging report that is displayed on the screen. I'm trying to work with one of the developers here to see if I can match one of the errors to a PID to get a better idea of what's happening. 

Below are 2 examples. I'm not even sure if this is something that we should be worried about. 

Jennifer

org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError: Cannot parse 'mods_subject_geographic_ms:"Bolton ': Lexical error at line 1, column 36.  Encountered: <EOF> after : "\"Bolton "
19:44:05SEVERESolrCoreorg.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError: Cannot parse 'mods_subject_topic_ms:"Railroads ': Lexical error at line 1,​ column 34. Encountered: <EOF> after : "\"Railroads "
org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError: Cannot parse 'mods_subject_topic_ms:"Railroads ': Lexical error at line 1, column 34.  Encountered: <EOF> after : "\"Railroads "

Diego Pino

unread,
Feb 11, 2016, 4:03:08 PM2/11/16
to isla...@googlegroups.com
Hi, are those fields in you advanced search settings?
It's not document related. So you don't have bad metadata (i'm supposing here). Solr is failing on a search, which means "someone" is passing wrong encoded stuff to a field as value in a query. Which can be in your advance solr search ding. not a (e)dismax search.
It could be also something related to encoding in faceting? does this match a facet? mods_subject_geographic_ms:"Central Street"?
You can look for wrong links in the facets if this happens there and also analyse those fields in the Solr Admin to get a better view.

Cheers


--
For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---
You received this message because you are subscribed to a topic in the Google Groups "islandora" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/islandora/KbcWdXUlPOc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to islandora+...@googlegroups.com.
Visit this group at https://groups.google.com/group/islandora.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/445331ea-4256-473a-b483-c7831c57a1c1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Jennifer Eustis

unread,
Feb 11, 2016, 5:48:16 PM2/11/16
to islandora
That helps. To answer your question, the mods_subject....ms is one of the fields we sort on and that we configured in Islandora/Solr. I was wondering if I change this to supersort or _ss if that would make a difference. I'll guess I'll try that. 

Jennifer
Reply all
Reply to author
Forward
0 new messages