[
https://issues.apache.org/jira/browse/SOLR-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645751#action_12645751
]
Mark Harwood commented on SOLR-839:
-----------------------------------
A couple of comments, Erik.
You can probably look to cache the CorePlusExtensionsQueryParser - it's
designed to be threadsafe.
One alternative interface you can possibly look at providing also is to let
clients send name/value pairs as criteria (e.g. typical HTML form input) and
use QueryTemplateManager along with XSL files in Solr server to map the input
parameters into executable XML. This keeps the client interface freer of
Lucene internals e.g. filters vs queries etc and the Solr administrator able to
maintain and tweak the appropriate query templates.
QueryTemplateManager is described in contrib unit tests and also written up in
my LIA2 contribution (I posted this to Mike McCandless)
Cheers
Mark
> XML Query Parser support
> ------------------------
>
> Key: SOLR-839
> URL: https://issues.apache.org/jira/browse/SOLR-839
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.3
> Reporter: Erik Hatcher
> Assignee: Erik Hatcher
> Fix For: 1.4
>
> Attachments: lucene-xml-query-parser-2.4-dev.jar, SOLR-839.patch
>
>
> Lucene contrib includes a query parser that is able to create the
> full-spectrum of Lucene queries, using an XML data structure.
> This patch adds "xml" query parser support to Solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
