ted in this. Any idea on when this will be
available?
Thanks
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 1:44 AM
To: solr-user@lucene.apache.org
Subject: Re: C# API for Solr
Well, i think there will be a lot of people who will be very
I would be very interested in this. Any idea on when this will be available?
Thanks
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 1:44 AM
To: solr-user@lucene.apache.org
Subject: Re: C# API for Solr
Well, i think there will be a lot
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
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
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
It would be great to have solr-ruby (the library formerly known as
solrb) included with Solr distributions, as well as Flare too. It
would give these libraries visibility and usability they'd not see if
they required additional downloads or "svn co". I can certainly say
that solr-ruby doe
: One administrative question: can I contribute these files to be stored under
: /lucene/solr/trunk/client? I don't have a handy place for making these
: publicly accessible at the moment.
yeah, as long as you can submit them in a Jira issue and legally check the
"grant apache liscence" radio bu
Good thought, Yonik. I haven't looked at the Java client, would certainly
be worthwhile. I'll move to prepping the files so they're completely
generic and can work for anyone.
One administrative question: can I contribute these files to be stored under
/lucene/solr/trunk/client? I don't have a
On 3/31/07, Jeff Rodenburg <[EMAIL PROTECTED]> wrote:
As we've proceeded, we've built out a nice C# client library to abstract the
interaction from C# to Solr. It's mostly generic and designed for
extensibilty. With a few modifications, this could be a stand-alone library
that works for others.
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 to make modifications through 2006. We quickly learned that
search management is so much more than query algorithms and indexing
choices. W
11 matches
Mail list logo