Looks like I ran into the same as was discussed here: http://grokbase.com/t/lucene/solr-user/15c4nr1j48/solrcloud-1-server-1-configset-multiple-collections-multiple-schemas
Would be nice if that would be changed in the future as it would make these setups much easier. On 29/04/16 20:07, Hendrik Haddorp wrote: > Hi, > > I have a Solr Cloud 6 setup with a managed schema. It seems like when I > create multiple collections from the same config set that they still > share the same schema. That was rather unexpected, as in the REST and > SolrJ API I do specify a collection when doing the schema change. > Looking into what is stored in ZooKeeper I do however only see a config > name stored for my collections so I guess this is the design. Or am I > missing something? Do I really need to upload a new config set when I > want to create a collection with unique fields? If so I would need to > make sure to delete that once I delete my collection. Seems a bit odd > and complicated to me. > > SolrJ is also behaving strange. When I try to add multiple fields using > a MultiUpdate request where two fields already exist and one is new I > get no error back (getStatus() == 0) while the response object contains > error messages for the fields that existed already and the new field did > not get added. > > regards, > Hendrik
