[
https://issues.apache.org/jira/browse/SOLR-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003505#comment-13003505
]
Ryan McKinley commented on SOLR-2409:
-------------------------------------
From:
https://issues.apache.org/jira/browse/SOLR-1553?focusedCommentId=12994448&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12994448
Adding:
{code:java}
// Make sure the Boolean Query actually has somethign there
if( parsedUserQuery instanceof BooleanQuery ) {
if( ((BooleanQuery)parsedUserQuery).getClauses().length < 1 ) {
parsedUserQuery = null;
}
}
{code}
seems to fix thigns.
I don't understand the bigger picture well enough to know the implications
> edismax unescaped colon returns no results
> ------------------------------------------
>
> Key: SOLR-2409
> URL: https://issues.apache.org/jira/browse/SOLR-2409
> Project: Solr
> Issue Type: Bug
> Components: search
> Reporter: Ryan McKinley
> Priority: Minor
> Attachments: SOLR-2409-unescapedcolon.patch
>
>
> The edismax query parser should behave OK when a colon is in the query, but
> does not refer to a field name.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
