On 5/6/2013 7:44 AM, Jack Krupansky wrote: > I think if we had a more compehensible term for a "collection > configuration directory", a lot of the confusion would go away. I mean, > what the heck is an "instance" anyway? How does "instanceDir" relate to > an "instance" of the Solr "server"? Sure, I know that it is the parent > directory of the collection configuration (conf directory) or a > "collection directory", but how would a mere mortal grok that? I mean, > "instance" sounds like it's at a higher level than the collection itself > - that's why people tend to think it's the same for all cores in a Solr > "instance". > > We should reconsider the name of that term. My choice: collectionDir.
I think that might lead to just as much confusion as instanceDir, because it's for a core, not a collection. A name like coreDir would avoid that confusion. If you actually are using collections, then you'll be using SolrCloud. A SolrCloud installation with maxShardsPerNode>1 will have more than one core for the same collection on each node, so collectionDir would be very confusing. I was initially thinking a good name would be coreConfDir or confDir, but that only makes sense in situations where dataDir is also present. The Collections API creates cores without a dataDir parameter, and many solr.xml files are created manually without dataDir. Thanks, Shawn
