[ 
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575459#action_12575459
 ] 

Yonik Seeley commented on SOLR-334:
-----------------------------------

So I recently added a nested query parser... it's useful to be able to allow 
the client to specify query parts but not know about them.

So a client could send bf=<!query v=$dateboost> to add a date boost, but the 
actual date boost query could be configured as a default on the server: 
dateboost=<!func>recip(rord(datefield,1,1000,1000))

I'm finding the local params stuff very useful, but I hate the fact that when I 
type the following URL in firefox, it transforms all the special chars.  It 
makes it very hard to edit (I use a browser a lot for testing).  Also, < would 
need to be escaped in any XML config too.

Example:  I type in
  http://localhost:8983/solr/select?q=<!dismax qf='title^10 body'>foo
But then firefox transforms it to
  http://localhost:8983/solr/select?q=%3C!dismax%20qf='title^10%20body'%3Efoo

So while things are still changeable (before a release), is this really the 
right syntax?
We could alternately go with [! which doesn't have this problem (and wouldn't 
have to be escaped in XML config either).
So it could look like:
  http://localhost:8983/solr/select?q=[!dismax qf='title^10 body']foo
Which firefox changes to
  http://localhost:8983/solr/select?q=[!dismax%20qf='title^10%20body']foo

Thoughts?

> 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.

Reply via email to