[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591069#action_12591069
]
[EMAIL PROTECTED] edited comment on SOLR-334 at 4/21/08 2:19 PM:
------------------------------------------------------------
It's not a single character at the start... it is currently <!
I actually like the look of the curly braces (looks like a map), but using both
types at once would make me always forget which came first (and it's uglier).
So here are some more ideas:
{code}
!{a=1}
{{a=1}}
[[a=1]]
{code}
was (Author: [EMAIL PROTECTED]):
It's not a single character at the start... it is currently <!
I actually like the look of the curly braces (looks like a map), but using both
types at once would make me always forget which came first (and it's uglier).
So here are some more ideas:
!{a=1}
{{a=1}}
[[a=1]]
> 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.
