Can I just start by saying that this was AMAZING. :-) When I asked the question, I certainly did not expect this level of details.
And I vote on the cake diagram for WIKI as well. Perhaps, two with the first one showing the trivial collapsed state of single collection/shard/replica/core. The trivial one will also help to explain why the example is now called 'collection1'. I think I followed everything, except for just added term of 'index'. Isn't that the same as 'core'? Or can we have several indexes in one core? Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Fri, Jan 4, 2013 at 10:11 AM, darren <dar...@ontrenet.com> wrote: > This is the containment hierarchy i understand but includes both physical > and logical. > > -------- Original message -------- > From: darren <dar...@ontrenet.com> > Date: > To: dar...@ontrenet.com,yo...@lucidworks.com,solr-user@lucene.apache.org > Subject: Re: Terminology question: Core vs. Collection vs... > > Actually. Node/collection/shard/replica/core/index > > > > -------- Original message -------- > From: darren <dar...@ontrenet.com> > Date: > To: yo...@lucidworks.com,solr-user@lucene.apache.org > Subject: Re: Terminology question: Core vs. Collection vs... > > > Agreed. But for completeness can it be node/collection/shard/replica/core? > >
