Mark - I've done a quick implementation here:
<https://issues.apache.org/jira/browse/SOLR-839>
I'm not familiar, yet, with what it takes (haven't read your
contribution to LIA2 yet, bad, Erik, bad) to configure it - so any
feedback you have on what might be needed beyond this is welcome:
public Query parse() throws ParseException {
CorePlusExtensionsParser parser = new
CorePlusExtensionsParser(getReq().getSchema().getQueryAnalyzer(),
getReq().getSchema().getSolrQueryParser(null));
try {
return parser.parse(new
ByteArrayInputStream(getString().getBytes()));
} catch (ParserException e) {
throw new ParseException(e.getMessage());
}
}
Erik
On Nov 5, 2008, at 5:31 AM, mark harwood wrote:
How about simply adding a query parser plugin to Solr using the
XML query parser?
My initial concern is to make public in Lucene/contrib the demo web
app I have just written up for Lucene In Action 2. I wanted to put
this in Lucene/contrib rather than limit it to being code
distributed with the book.
This aside, I think it's generally important to maintain
documentation/demos/code and other useful resources under the core
Lucene project for those people where Solr might not necessarily be
the answer.
I'd be happy to help or to even go the full distance and implement
it myself.
Adding XML query support to Solr certainly sounds like it would be a
sensible idea. I think applications with advanced query criteria
struggle with the constraints of standard Lucene QueryParser syntax
or passing "flat" parameters in Solr urls.
Not sure I can commit any time to extending Solr myself but happy to
support you with any guidance you may need on this.
Cheers,
Mark
----- Original Message ----
From: Erik Hatcher <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Wednesday, 5 November, 2008 10:48:48
Subject: Re: Adding dependency to servlet-api
Mark,
How about simply adding a query parser plugin to Solr using the XML
query parser? It'd be pretty short, sweet, easy, and a real value-
add to Solr too! I'd be happy to help or to even go the full
distance and implement it myself. I've considered it often, as it
would be great to provide the breadth of query types that your
parser can create.
Erik
On Nov 5, 2008, at 4:16 AM, mark harwood wrote:
Just checked Solr (forgot about that obvious precedent!) and they
have it in trunk/lib and an entry in trunk/notice.txt which reads:
" Includes software from other Apache Software Foundation
projects, including, but not limited to:
....
- Apache Tomcat (lib/servlet-api-2.4.jar)
....
"
I thought the servlet api was Sun's to be honest so not sure why it
is credited to Tomcat.
I could just follow this precedent. Anyone from the Solr camp care
to comment?
----- Original Message ----
From: Uwe Schindler <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org; [EMAIL PROTECTED]
Sent: Wednesday, 5 November, 2008 9:53:51
Subject: RE: Adding dependency to servlet-api
E.g. Jetty webserver (Apache 2.0 License) ships the servlet 2.5 API
in
source (SVN) and binary form along with its web container server.
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [EMAIL PROTECTED]
From: Konstantin Priblouda [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 10:42 AM
To: java-dev@lucene.apache.org
Subject: Re: Adding dependency to servlet-api
----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/
--- On Tue, 11/4/08, markharw00d <[EMAIL PROTECTED]> wrote:
From: markharw00d <[EMAIL PROTECTED]>
Subject: Adding dependency to servlet-api
To: java-dev@lucene.apache.org
Date: Tuesday, November 4, 2008, 11:09 PM
I'd like to add a web-based demo for the XML QueryParser
but unlike the existing web demo I'd prefer to use some
Java code that gets compiled rather than doing it all in JSP
files that aren't part of the build. Doing it this way
will add a dependency on servlet-api.jar which will need to
be added to the build somehow.
Has anyone done this before on an Apache project before and
know what the license implications are? Tomcat/Struts must
do this already but I'm not sure what is involved.
Geronimo project provides servlet api declarations in m2
repository on
apache.
Usually this is agood choice.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
