related: it would be nice if the coming/going of cores didn't necessitate changing solr.xml
Perhaps every directory under the solr home could implicitly define a collection.

+1

related: it would be nice if the coming/going of cores didn't necessitate changing solr.xml Perhaps every directory under the solr home could implicitly define a collection.

Yea, been thinking the same. How about a "my-core/collection.properties" file to set the various props? If file exists but is empty it could be a simple marker that this is a core and assume defaults for all settings. And how about adding SOLR_HOME/lib as shared lib folder by convention and SOLR_HOME/core/lib as core-specific lib folder? We might then not need solr.xml at all?

We should create another issue for that (though it would be easier to do on a major release perhaps) - I'll commit this quick change in a bit to make sure we have at least this improvement.

hoss20120711-manual-post-40alpha-change

> related: it would be nice if the coming/going of cores didn't necessitate changing solr.xml
> Perhaps every directory under the solr home could implicitly define a collection.

Not a good idea. We unload cores to save memory on some machines, then load them on demand. This would make it much harder for us to accomplish.

Also, what would happen if a core was unloaded?

We would still support loading and unloading.

Also, what would happen if a core was unloaded?

The simple properties file or whatever in each core folder would indicate the core was not 'loaded'. Or one of many other solutions.