Thanks again Otis. Few more questions, 1) My app currently is a stand-alone java app (not part of Solr JVM) that simply calls update webservice on Solr (running in a separate web container) passing 10k documents at once. In your example you mentioned getting list of Indexers and adding document to them manually - do you mean I use Lucene directly in my app to do the indexing and use Solr just for search purposes? How can I simply write to different cores (using Solr webservice) without putting Lucene code in my app?
2) In MultiCore example on Wiki shows pre-configured cores in the solr.xml. How can I create cores on fly from my app - is there a command (or web service) to tell Solr to load new core? For ex., every day I want to create a new core for that day on fly and index in that core only. Also, would I be able to search on cores created on fly? Currently, I'm using standard out-of-box requests and response handlers for Solr. Would using multi-core require any custom handlers? Thanks, -vivek On Thu, Mar 26, 2009 at 10:38 AM, Otis Gospodnetic <otis_gospodne...@yahoo.com> wrote: > > Hi, > > 1) Look for "multicore" on Solr Wiki > > 2) I meant to say you would not index it all in one index (that's what you > wanted to do, no?). So in your app you'd do something like > ts = doc.getTimestamp(); > indexer = getIndexer(ts); // gives you different indexer based on the ts. > You keep track of all the indexers (e.g. all instances of solr client you > have in your app, each of which points to a different solr server/core/index) > indexer.index(doc); > > > If your issue is large indices and search performance, then the solution is > not to have multiple solr cores/indices per machine as much as distributed > indexing (multiple servers). Look at DistributedSearch page on the Wiki. > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > >
