Erik Hatcher schrieb:
On Jan 24, 2007, at 9:38 AM, Maximilian Hütter wrote:
Erik Hatcher schrieb:
On Jan 22, 2007, at 4:09 AM, Maximilian Hütter wrote:
Is there
a XMLQueryParser yet? I didn't find it in the source.
Yes - it's part Lucene's contrib area:
On 1/31/07, Maximilian Hütter [EMAIL PROTECTED] wrote:
Posting a normal query-string would be fine, but that doesn't seem to
work... I tried the solr-1.1.0 with Jetty (as in the tutorial) using curl.
My request: curl -F q=solr http://localhost:8983/solr/select/ (after
loading the xml examples)
Erik Hatcher schrieb:
On Jan 22, 2007, at 4:09 AM, Maximilian Hütter wrote:
Is there
a XMLQueryParser yet? I didn't find it in the source.
Yes - it's part Lucene's contrib area:
http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/xml-query-parser/
You'll have to build
On Jan 24, 2007, at 9:38 AM, Maximilian Hütter wrote:
Erik Hatcher schrieb:
On Jan 22, 2007, at 4:09 AM, Maximilian Hütter wrote:
Is there
a XMLQueryParser yet? I didn't find it in the source.
Yes - it's part Lucene's contrib area:
Thank you for the answers, the idea was to use Solr with REST. Is there
a XMLQueryParser yet? I didn't find it in the source.
Max
Erik Hatcher schrieb:
Also consider that I expect Solr to support the XMLQueryParser at some
point in the near future, which would be POSTed in a body for a search
On Jan 22, 2007, at 4:09 AM, Maximilian Hütter wrote:
Is there
a XMLQueryParser yet? I didn't find it in the source.
Yes - it's part Lucene's contrib area:
http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/xml-query-
parser/
You'll have to build the JAR and put it into Solr's
On Jan 21, 2007, at 11:12 PM, Yonik Seeley wrote:
On 1/21/07, Erik Hatcher [EMAIL PROTECTED] wrote:
Yes, I think different syntaxes in different places would be useful.
For example, a user enters a full-text search query that is suitable
to use with Solr's QueryParser, and then the user facets
On 1/22/07, Erik Hatcher [EMAIL PROTECTED] wrote:
On Jan 21, 2007, at 11:12 PM, Yonik Seeley wrote:
On 1/21/07, Erik Hatcher [EMAIL PROTECTED] wrote:
Yes, I think different syntaxes in different places would be useful.
For example, a user enters a full-text search query that is suitable
to
: 4) now it's easy to subclass StandardRequestHandler as
: XmlQuerySyntaxRequestHandler or SurroundSyntaxRequestHandler
: just by overriding getQUeryParser.
: Blech. All the other ideas are good, and rather orthogonal to
: declaring the syntax in the query itself.
yeah ... i didn't say i
On 1/21/07, Erik Hatcher [EMAIL PROTECTED] wrote:
On Jan 20, 2007, at 9:23 PM, Chris Hostetter wrote:
: In the back of my mind, I've been thinking about *how* to support
: multiple query syntaxes.
: trying to add new parameters everywhere specifying the type
doesn't
: seem like a great
On 1/21/07, Yonik Seeley [EMAIL PROTECTED] wrote:
Another syntax option... something like
!term:myfield:my unescaped value all as a singe term
#term:
%term:
@term:
(basically, find a prefix that would be unlikely to appear as an
actual term or wildcard in lucene queryparser syntax)
More
: In the back of my mind, I've been thinking about *how* to support
: multiple query syntaxes.
: trying to add new parameters everywhere specifying the type doesn't
: seem like a great idea (way too many places).
: Good point. Yeah, it does make sense for the query type to be part
: of the
On 1/20/07, Chris Hostetter [EMAIL PROTECTED] wrote:
: In the back of my mind, I've been thinking about *how* to support
: multiple query syntaxes.
: trying to add new parameters everywhere specifying the type doesn't
: seem like a great idea (way too many places).
: Good point. Yeah, it
: Some syntaxes might come by default from solrcondig.xml, and some
: might come from the request.
: Also, if you just needed one span query, you wouldn't want to force
: all other queries to be in the same syntax. Think about having to
: change your faceting code that uses QueryParser queries
On 1/19/07 10:02 AM, Brian Lucas [EMAIL PROTECTED] wrote:
Walter Underwood wrote:
Use GET unless it really, really, really doesn't work. POST is
the wrong HTTP semantic for fetching information. Long query
strings are not a good enough reason. HTTP puts no limit on the
length of a URL.
On 1/19/07, Brian Lucas [EMAIL PROTECTED] wrote:
Walter Underwood wrote:
Use GET unless it really, really, really doesn't work. POST is
the wrong HTTP semantic for fetching information. Long query
strings are not a good enough reason. HTTP puts no limit on the
length of a URL.
Walter,
On 1/19/07, Erik Hatcher [EMAIL PROTECTED] wrote:
Also consider that I expect Solr to support the XMLQueryParser at
some point in the near future
I had always planned on supporting an XML query format, but I never
got a chance to review the XMLQueryParser now in Lucene to see if I
like it. Do
17 matches
Mail list logo
