First of all, in reference to
http://www.mail-archive.com/solr-user@lucene.apache.org/msg00808.html ,
I got it working! The problem(s) was coming from solPHP; the
implementation in the wiki isn't really working, to be honest, at least
for me. I had to modify it significantly at multiple places
From: Michael Imbeault [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 09, 2006 12:30 PM
To: solr-user@lucene.apache.org
Subject: Got it working! And some questions
First of all, in reference to
http://www.mail-archive.com/solr-user@lucene.apache.org/msg00808.html ,
I got it working! The pr
rray($array)" in the example, because it accepts an array of
updates) but I'd definitely like to see how you revised it.
Thanks,
Brian
-Original Message-
From: Michael Imbeault [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 09, 2006 12:30 PM
To: solr-user@lucene.apache.org
: - What is the loadFactor variable of HashDocSet? Should I optimize it too?
this is the same as the loadFactor in a HashMap constructor -- but i don't
think it has much affect on performance since the HashDocSets never
"grow".
I personally have never tuned the loadFactor :)
: - What's the unit
First of all, it seems the mailing list is having some troubles? Some of
my posts end up in the wrong thread (even new threads I post), I don't
receive them in my mail, and they're present only in the 'date archive'
of http://www.mail-archive.com, and not in the 'thread' one? I don't
receive so
: First of all, it seems the mailing list is having some troubles? Some of
: my posts end up in the wrong thread (even new threads I post), I don't
: receive them in my mail, and they're present only in the 'date archive'
: of http://www.mail-archive.com, and not in the 'thread' one? I don't
: rec
On 9/9/06, Michael Imbeault <[EMAIL PROTECTED]> wrote:
The main problem was that addIndex was sending 1 doc at a time to solr;
it would cause a problem after a few thousand docs because i was running
out of resources.
Sending one doc at a time should be fine... you shouldn't run out of
resource
On Sep 10, 2006, at 10:47 PM, Michael Imbeault wrote:
I'm still a little disappointed that I can't change the OR/AND
parsing by just changing some parameter (like I can do for the
number of results returned, for example); adding a OR between each
word in the text i want to compare sounds s
Hello Erik,
Thanks for add that feature! "do" is fine with me, if "op" is already
used (not sure about this one).
Erik Hatcher wrote:
On Sep 10, 2006, at 10:47 PM, Michael Imbeault wrote:
I'm still a little disappointed that I can't change the OR/AND
parsing by just changing some parameter
On 9/11/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Sep 10, 2006, at 10:47 PM, Michael Imbeault wrote:
> I'm still a little disappointed that I can't change the OR/AND
> parsing by just changing some parameter (like I can do for the
> number of results returned, for example); adding a OR bet
: Maybe something like q.op or q.oper if it *only* applies to q. Which
: begs the question... what *does* it apply to? At first blush, it
: doesn't seem like it should apply to other queries like fq, facet
: queries, and esp queries defined in solrconfig.xml. I think that
: would be very surpri
On Sep 11, 2006, at 2:52 PM, Yonik Seeley wrote:
On 9/11/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Sep 10, 2006, at 10:47 PM, Michael Imbeault wrote:
> I'm still a little disappointed that I can't change the OR/AND
> parsing by just changing some parameter (like I can do for the
> numbe
: I've implemented the ability to override the default operator with
: q.op=AND|OR. The patch is pasted below for your review.
if i'm reading that right, one subtlety is that "new
SolrQueryParser(schema,field)" no longer pas attention to
schema.getQueryParserDefaultOperator() -- that only only b
On Sep 12, 2006, at 4:47 PM, Chris Hostetter wrote:
: I've implemented the ability to override the default operator with
: q.op=AND|OR. The patch is pasted below for your review.
if i'm reading that right, one subtlety is that "new
SolrQueryParser(schema,field)" no longer pas attention to
sche
: SolrQueryParser now knows nothing about the default operator, it is
: set from QueryParsing.parseQuery() when passed a SolrParams.
i didn't test it, but it looks clean to me.
the only other thing i would do is beaf up the javadocs for
SolrQueryParser (to clarify that IndexSchema is only used f
15 matches
Mail list logo
