lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Johnson" <wjohn...@GETCONNECTED.COM>
Subject RE: [jira] Commented: (SOLR 2 1 5) Multiple Solr Cores
Date Wed, 11 Jul 2007 17:26:14 GMT
Most of the time I, and I imagine others, don't know the set of core's
ahead of time.  It seems somewhat wasteful to create a ton of solr
server connections when a single one can handle things just as easily.
I guess I don't see why this param should be any different than any
others like output formats etc.    

As for POST's, you can still have cgi arguments and access them via the
same servlet request parameters while accessing the input stream.

I'll leave the efficiency issues to people more familiar with the patch
but if it has to be in the url then you force people using solrj and
other similar apis to create a Map<String, SolrServer> and manage them
that way.

- will

-----Original Message-----
From: yseeley@gmail.com [mailto:yseeley@gmail.com] On Behalf Of Yonik
Seeley
Sent: Wednesday, July 11, 2007 1:20 PM
To: solr-dev@lucene.apache.org
Subject: Re: [jira] Commented: (SOLR 2 1 5) Multiple Solr Cores

On 7/11/07, Will Johnson <wjohnson@getconnected.com> wrote:
> I think it would be nice to have the core name
> specified as a CGI param instead of (or in addition to) a url path.
> Otherwise, large section of client code (such as solrj/solr#) will
need
> to be changed.

Only if you want to talk to multiple cores over a single "connection",
right?
Hopefully existing client code will allow the specification of the URL,
and
one would use http://localhost:8983/solr/core1/

Still might be useful as a param *if* it can be done efficiently.
I wonder about the case when the param comes in via POST though.

-Yonik

Mime
View raw message