The starting point for Solr-215 was this http://www.nabble.com/Embedding-Solr-vs-Lucene%2C-multiple-Solr-cores--tf3572324.html thread in April. I'll still say that some of our customers IT are making deployment of multiple webapps something more complex than it should...but they do! IT is in fact managing an internal hosting service and do not want to deal with the functional part of the applications. In these environments, a webapp that starts a thread & uses the file system is already a hard sell...
In the same thread, I got the impression that removing the singletons would be useful anyway: hossman_lucene wrote: > >>That said: If anyone is interested in tackling a patch to eliminate all of >>the static Singletons i (and many others i suspect) would be >>extremely gratefull .. both for how much it would improve hte reusability >>of Solr in embedded situatiosn like this, but also for how it would >>(hopefully) make hte code eaier to follow for future developers. > More to your point, programmatic creation of indexes comes handy if you want to extend Solr with collection management (rather than dealing with them "externally" through scripts). You can easily add collections and/or languages and manage the collections definition/refresh/reindexing within the application; it seemed like a natural extension to the project. The main rationale being that since the Solr document/field format is most likely not the authoring format of the original "resource" (the authored source file), there is value in declaring how to transform a "resource" into an Solr-XML document from its collection/lang/suffix/etc. But this is beyond Solr-215. The same could be said for distributed search (aka solr-255) versus a 'Solr cluster management' application... At this point, Solr-215 just looks like a solution to my problem... My apologies for the clutter & waste of community resources. Yonik Seeley wrote: > > On 6/27/07, Henrib <[EMAIL PROTECTED]> wrote: >> This http://www.nabble.com/multiple-indices-tf3982573.html thread >> triggers >> the question again. >> Solr-215 makes it easier to deploy multiple indexes than using multiple >> web >> applications; but is "easier" enough for not being just a superfluous >> feature? > > With a fixed handful of indicies, IMO, no. > Though if one needs to programmatically add new indicies/schemas, > SOLR-215 becomes interesting. I don't know how common of a case that > is though. There are probably other use cases I've not considered. > > SOLR-215 does seem unrelated to distributed search though. > > -Yonik > > -- View this message in context: http://www.nabble.com/Multiple-indexes-cores-%28aka-solr-215%29-functional-value--tf3927076.html#a11327863 Sent from the Solr - Dev mailing list archive at Nabble.com.
