I did a little experimentation:
This query is sent down to Solr and performs a proper wildcard:
search(collection2, q="hel*", fl="id", sort="id asc")
This query properly escapes the wildcard:
search(collection2, q="hel\*", fl="id", sort="id asc")
So it appears that the main issue is with the d
Thanks for your help.
Yes, I think SOLR-10894 is exactly about the issue I have seen.
So if I understand correctly there is currently no way to create a method
in client code (like Drupal’s search_api_solr module) that takes arbitrary user
input
and escapes it to get *always* a valid expression
I just confirmed that the following query works as expected:
search(collection2, q="test_s:\"hello world\"", fl="id", sort="id desc")
In this case the double quotes are used to specify a phrase query.
But this fails:
search(collection2, q="test_s:\"hello world", fl="id", sort="id desc")
In thi
Also while looking at you're query it looks like you are getting error from
the solr query parser. I believe the this is the issue you are facing:
https://issues.apache.org/jira/browse/SOLR-10894
I'll confirm, but I believe this query should work:
search(collection1, q="test \"hello world\""...)
This ticket originally addressed the issue:
https://issues.apache.org/jira/browse/SOLR-8409
It's a confusing ticket though and I'm not seeing test cases that prove out
that this is still working. I write a quick test case to see how escaping
of quotes is being handled.
This is a followup issue w
