[
https://issues.apache.org/jira/browse/LUCENE-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499491#comment-13499491
]
Jack Krupansky commented on LUCENE-4271:
----------------------------------------
I don't see anything wrong with supporting parameterized queries and multiple
query parsers down at the lowest level of the Lucene Query Parser. I don't mean
to suggest that the Lucene Query Parser should know directly about the
Solr-level structures such as the Solr schema, Solr "params", and Solr Q Parser
plugins, but I am suggesting that Lucene could declare and support abstractions
for those sorts of interfaces, and then the Solr-level Qparser/plugin would
supply all of them, and pure Lucene application could optionally use them as
well, either with additional query parser methods or subclassing. This should
also include full support for dismax fields and aliases as well. and things
like support for full negative queries.
There are lots of useful features which are available in the Solr query parsers
which are unavailable directly to Lucene apps without a lot of effort, and for
no good reason.
I mean, as long as these features don't impact performance or ease of
programming for simple Lucene apps, what possible legitimate objection could
there be?
The current "estrangement" between the Lucene and Solr query parsers is quite a
black eye for Lucene/Solr that can easily be remedied, at least from a
technical perspective.
In the context of this current Jira, why not provide an additional Lucene query
parser method to provide a simple keyword/value map of "parameters" that can be
substituted into a query? Seems to make solid sense to me!
> 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
> Attachments: LUCENE-4271.patch
>
>
> 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
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]
