[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526339
]
Yonik Seeley commented on SOLR-334:
-----------------------------------
OK, my next step is to do tests for all these new functions provided no one
sees an issue with the general approach.
I chose to stick with VaueSource as the basis for new functions rather than
CustomScoreQuery because of greater complexities with weights, scorers,
explanations, etc, and performance issues wrt scorers (skipTo, next needing to
know deleted docs).
> pluggable query parsers
> -----------------------
>
> Key: SOLR-334
> URL: https://issues.apache.org/jira/browse/SOLR-334
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
>
> One should be able to optionally specify an alternate query syntax on a
> per-query basis
> http://www.nabble.com/Using-HTTP-Post-for-Queries-tf3039973.html#a8483387
> Many benefits, including avoiding the need to do query parser escaping for
> simple term or prefix queries.
> Possible Examples:
> fq=<!term field="myfield">The Term
> fq=<!prefix field="myfield">The Prefix
> q=<!qp op="AND">a b
> q=<!xml><?xml...> // lucene XML query syntax?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
