[ 
https://issues.apache.org/jira/browse/LUCENE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424909#comment-13424909
 ] 

Yonik Seeley edited comment on LUCENE-4271 at 7/31/12 8:52 AM:
---------------------------------------------------------------

Each clause would have it's own... this is really about adding a LocalParams 
style query as a clause.
It's really just about the ability to leave off the _query_ magic field name 
and quotes in the current style of embedding one can already do in Solr.

Complex example:

{code}
+foo -bar +{!baz arg=val} word -{!raw f=myfield v="the raw term"} +anotherword
{code}
                
      was (Author: [email protected]):
    Each clause would have it's own... this is really about adding a 
LocalParams style query as a clause.
It's really just about the ability to leave off the _query_ magic field name 
and quotes in the current style of embedding one can do.

Complex example:

{code}
+foo -bar +{!baz arg=val} word -{!raw f=myfield v="the raw term"} +anotherword
{code}
                  
> Solr LocalParams for Lucene Query Parser
> ----------------------------------------
>
>                 Key: LUCENE-4271
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4271
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>
> The Lucene QueryParser should implement Solr's LocalParams syntax directly so 
> that instead of
> {code}
> _query_:"{!geodist d=10 p=20.5,30.2}"
> {code}
> one could directly use
> {code}
> {!geodist d=10 p=20.5,30.2}
>  {code}
> references: http://wiki.apache.org/solr/LocalParams

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to