On Mar 8, 2013, at 2:57 PM, Steve Rowe <sar...@gmail.com> wrote: >> multiple collections may share the same config set and thus schema, so what >> happens if someone does not know this and hits PUT >> localhost:8983/solr/collection1/schema and it affects also the schema for >> collection2? > > Hmm, that's a great question. Querying against a named config rather than a > collection/core would not be an improvement, though, since the relationship > between the two wouldn't be represented in the request. > > Maybe if there were requests that returned the collections using a particular > named config, and vice versa, people could at least discover problematic > dependencies before they send schema modificaiton requests? Or maybe such > requests already exist?
Also, this doesn't have to be either/or (collection/core vs. config) - we could have another API that's config-specific, e.g. for the fields resource: collection-specific: http://localhost:8983/solr/collection1/schema/fields config-specific: http://localhost:8983/solr/configs/configA/schema/fields Steve
