So the thing is ... these collections all have very unique schemas and the data 
are unrelated to each other.  And we do a lot of field queries on the content.  
We would not want the data from one collection to ever show up in another 
collection query.  They are used by different audiences and securities as well. 
 We want to keep them separated.  

While it is not required that the urls include the myParentX ... it would be 
consistent with our current implementation that we are upgrading from 4.6 to 
7.2.  this was a very simple task under apache but I cant figure out how to do 
this in solr 7

-----Original Message-----
From: Becky Bonner 
Sent: Friday, March 2, 2018 1:11 PM
To: 'solr-user@lucene.apache.org' <solr-user@lucene.apache.org>
Subject: RE: solr url control

Sorry Webster - I meant to make this a new question ... but accidentally sent 
it. You wrote
From: Webster Homer [mailto:webster.ho...@sial.com] 
Sent: Friday, March 2, 2018 12:20 PM
To: solr-user@lucene.apache.org
Subject: Re: NRT replicas miss hits and return duplicate hits when paging 
solrcloud searches

Becky,
This should have been its own question.

Solrcloud is different from standalone solr, the configurations live in 
Zookeeper and the index is created under SOLR_HOME. You might want to rethink 
your solution, What problem are you trying to solve with that layout? Would it 
be solved by creating the Parent1 collection with 2 shards?

-----Original Message-----
From: Becky Bonner 
Sent: Friday, March 2, 2018 11:29 AM
To: solr-user@lucene.apache.org
Subject: solr url control

We are trying to setup one solr server for several applications each with a 
different collection.  Is there a way to have have 2 collections under one 
folder and the url be something like this:
http://mysolrinstance.com/solr/myParent1/collection1
http://mysolrinstance.com/solr/myParent1/collection2
http://mysolrinstance.com/solr/myParent2
http://mysolrinstance.com/solr/myParent3


We organized it like that under the solr folder but the URLs to the collections 
do not include the "myParent1".
This makes the names of my collections more confusing because you can't tell 
what application they belong to.  It wasn’t a problem until we had 2 
collections for one of the apps.

Reply via email to