Hi, What about using the delta-import command of the DIH? http://wiki.apache.org/solr/DataImportHandler#Using_delta-import_command
If you want two have 2 separated indexes, you could play with the "swap" command. One index would be continuously updated and the other one used for the user requests. >From time two time you will have to "swap" to that users get the most recent data. http://wiki.apache.org/solr/CoreAdmin (swap part). Marc. On Fri, Dec 9, 2011 at 10:46 AM, BenMccarthy <ben...@gmail.com> wrote: > Good Morning. > > I have now been through the various Solr tutorials and read the SOLR 3 > Enterprise server book. Im not at the point of figuring out if Solr can > help us with a scaling problem. Im looking for advice on the following > scenario any pointers or references will be great: > > I have two sets of distinct data: > > Advert > Advertiser > > An Advertiser has many Adverts in the db looking like > > Advert { > id > field a > field b > advertiser_id > } > > Advertiser { > id > field c > field d > lat > long > } > > So ive followed some docs and ive created a DIH which pulls all this into > one SOLR index. Which is great. The problem im looking at is that we have > a massive churn on Advertiser updates and with the one index i dont think > it > will scale (Correct me if im wrong). > > Would it be possible to have two seperate cores each with its own index and > then when issuing queries the results are returned as they are in a single > core setup. > > Im basically looking for some pointers telling me if im going in the right > direction. I dont want to have to update 50000 adverts when a advertiser > simply updated field c. This is a problem we have with our current search. > > Thanks > Ben > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Best-Practice-Configuration-tp3572492p3572492.html > Sent from the Solr - User mailing list archive at Nabble.com. >
