Why do you need the merged core? If the underlying data is changing then obviously the merged core won't automatically update it self. And another merge will introduce duplicate data. So this is a bad solution.
You can just keep the two cores and do a distributed search across both of them? You can specify shards=http://localhost:8983/solr/ <http://localhost:8983/solr/admin/cores?action=mergeindexes&core=core3&srcCore=sitecore_web_index&srcCore=core2> core1,http://localhost:8983/solr/ <http://localhost:8983/solr/admin/cores?action=mergeindexes&core=core3&srcCore=sitecore_web_index&srcCore=core2>core2 as a parameter to your search requests. On Thu, Jul 7, 2016 at 4:32 AM, Kalpana <ksivanan...@portalsolutions.net> wrote: > Hello > > I have two sources - Sitecore web index (core 1) and a database table (core > 2). I have created core 3 which is a merge of core1 and core 2. > > > http://localhost:8983/solr/admin/cores?action=mergeindexes&core=core3&srcCore=sitecore_web_index&srcCore=core2 > > But when someone publishes a page on Sitecore, the sitecore web index gets > updated but not the merged core. How can get the real time data with the > merge? Is there a way? > > Thanks > Kalpana > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-Merge-Index-tp4286081.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Regards, Shalin Shekhar Mangar.
