[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591045#action_12591045
]
Hoss Man commented on SOLR-334:
-------------------------------
well, at hte very least i would suggest using {...} instead of [...] since
square brackets already have meaning in the primary query parser syntax.
from a huffman encoding standpoint, i would also argue that a multi character
delimiter (ie: {[...]} ) is better then a single character since it's the
atypical behavior. things people type frequently should be easier then the
things they type infrequently ... let's not make this too easy.
> pluggable query parsers
> -----------------------
>
> Key: SOLR-334
> URL: https://issues.apache.org/jira/browse/SOLR-334
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Attachments: qparser.patch, qparser.patch, qparser.patch
>
>
> 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.
