This did the trick
localhost:8983/solr/sitecore_web_index,localhost:8983/solr/SharePoint_All
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Merge-Index-tp4286081p4286272.html
Sent from the Solr - User mailing list archive at Nabble.com.
Some more info:
I am using Solrnet in my MVC project for search results:
var urlHealthInfo = ConfigurationManager.AppSettings["solrSPHealthInfo"] !=
null ?
ConfigurationManager.AppSettings["solrSitecoreSPHealthInfo"].ToString() :
"http://localhost:8983/solr/Sitecore_SharePoint_HealthInformation";
Thanks for your reply.
I am using Solrnet to set up the search object. Is it possible to use the same
for sharding?
On Jul 7, 2016, at 4:11 AM, Shalin Shekhar Mangar [via Lucene]
mailto:ml-node+s472066n428613...@n3.nabble.com>>
wrote:
Why do you need the merged core? If the underlying data
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 ca
