[
https://issues.apache.org/jira/browse/SOLR-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620889#comment-13620889
]
Jan Høydahl commented on SOLR-3580:
-----------------------------------
Any progress on this?
A more compact config format would be possible too:
{code}
validOperators=or:OR,or and:AND,and not:NOT
{code}
Then, if we add more operators later, such as NEAR, the same param would apply.
Perhaps we also could use this to disable explicit operators alltogether by
allowing an empty list {{validOperators=or: and: not:}} - for people who want
to lock things down.
As for interaction with lowercaseOperators, I'm happy to let it hang around for
4.x, but throw an exception if both params are defined together.
> In ExtendedDismax, lowercase 'not' operator is not being treated as an
> operator when 'lowercaseOperators' is enabled
> --------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3580
> URL: https://issues.apache.org/jira/browse/SOLR-3580
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 4.0-ALPHA
> Reporter: Michael Dodsworth
> Priority: Minor
> Attachments: SOLR-3580.patch, SOLR-3580-proposal.patch
>
>
> When lowercase operator support is enabled (for edismax), the lowercase 'not'
> operator is being wrongly treated as a literal term (and not as an operator).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
