Hello, I'm having usage issues with *Solrcloud*.
What I want to do: - Manage a solr server *only with the API* (create / reload / delete collections, create / replace / delete fields, etc). - A new collection should* start with pre-defined default fields, fieldTypes and copyFields* (let's say, field1 and field2 for fields). - Each collection must *have its own schema*. What I've setup yet: - Installed a *Solr 5.3.1* in //opt/solr/ on an Ubuntu 14.04 server - Installed *Zookeeper 3.4.6* in //opt/zookeeper/ as described in the solr wiki - Added line "server.1=127.0.0.1:2888:3888" in //opt/zookeeper/conf/zoo.cfg/ - Added line "<str name="zkHost">127.0.0.1:2181</str>" in //var/solr/data/solr.xml/ - Told solr or zookeeper somewhere (don't remember where I setup this) to use //home/me/configSet/managed-schema.xml/ and //home/me/configSet/solrconfig.xml/ for configSet - Run solr on port 8983 My //home/me/configSet/managed-schema.xml/ contains *field1* and *field2*. Now let's create a collection: http://my.remote.addr:8983/solr/admin/collections?action=CREATE&name=collection1&numShards=1 - *collection1 *is created, with *field1 *and *field2*. Perfect. Let's create another collection: http://my.remote.addr:8983/solr/admin/collections?action=CREATE&name=collection2&numShards=1 - *collection2 *is created, with *field1 *and *field2*. Perfect. No, if I *add some fields* on *collection1 *by POSTing to : /http://my.remote.addr:8983/solr/collection1/schema/ the following: - *field3 *and *field4 *are successfully added to *collection1* - ... but they are *also added* to *collection2* (verified by GETting /http://my.remote.addr:8983/solr/collection2/schema/fields/) How to prevent this behavior, since my collections have *different kind of datas*, and may have the same field names but not the same types? Thanks, Ben -- View this message in context: http://lucene.472066.n3.nabble.com/Solrcloud-1-server-1-configset-multiple-collections-multiple-schemas-tp4243584.html Sent from the Solr - User mailing list archive at Nabble.com.
