[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586960#action_12586960
]
Hoss Man commented on SOLR-334:
-------------------------------
I'd vote for anything but "<" ... mainly because of the XML similarity and
escaping needed..
square brackets or curly braces are fine with me ... we could even go with a
combo approach to reduce the likelyhood of collision with any existing/future
syntax people want to write QParser plugins for....
bq. bf={[!query v=$dateboost]}
...OR... and call me crazy here ... we could make the actual start/end tokens
be configurable (could make sense as a <requestParser> option since using
different markup per handler seems like overkill)
> 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.
