Well, i think there will be a lot of people who will be very happy with
this C# client.
grts,m
"Jeff Rodenburg" <[EMAIL PROTECTED]>
31/03/2007 18:00
Please respond to
solr-user@lucene.apache.org
To
solr-user@lucene.apache.org
cc
Subject
C# API for Solr
We built our first search sys
Thk u Chris.
i just wanna know how to manage master and slaver hardware, for example ram
and disc 's size.
2007/3/31, Chris Hostetter <[EMAIL PROTECTED]>:
: if we mv index.tmp$$ index,,,is it truly deleted?
it's not treuly deleted until no running processes have the file handles
open anym
Ryan - I'm working on cleanup to release this thing for the world to enjoy.
-- j
On 3/31/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Yes yes!
On 3/31/07, Jeff Rodenburg <[EMAIL PROTECTED]> wrote:
> We built our first search system architecture around Lucene.Net back in
2005
> and continued
I agree fully, for me the PHP client API in the works should be including a
good set of unit tests.
The channel dilemma also shows up, as in the PHP ecosystem there are at
least 2 major ones to hook up.
Personally I would go for eZ components as this already provides a good
framework with unit t
Yes, it is only solr - and will have a normal HTTP interface, no lucene.
But as i said, the catch is that *all* fields must be stored, not only
the ones you want to change. Solr will pull the document out of the
index, modify it and put it back - it can only pull out stored fields
so you must st
Hello Ryan,
Interesting. So it's solr only and does not require new Lucene
functionality? I think storing the fields that may change in
the future is ok.
--
Best regards,
Jack
Saturday, March 31, 2007, 5:50:20 PM, you wrote:
> Lucene does not have any way to modify existing fields, so solr can
What would make things consistent for the client api's is a prescribed set
of implementations for a solr release. For example, executing searches with
these parameters, support for facets requires those parameters, updates
should be called in this manner, etc. For lack of a better term, a
loosel
I've read through the list entries here, the Lucene list, and the wiki docs
and am not resolving a major pain point for us. We've been trying to
determine what could possibly cause us to hit this in our given environment,
and am hoping more eyes on this issue can help.
Our scenario: 150MB index
