> Sure it does. Well, it fits mine at least :) The server has
> the choice to search one or more indexes when it gets
> serverChoice, which is what it gets when there's no index.
>
> If the server is always just going to search one default
> index, then it can say so in Explain.
>
> Ralph's underlying index is not a single field, but there's
> no requirement that indexes should be.
Ralph may correct me but his "BasicIndex" which is searched when the
index is omitted is a conjunction of multiple "indexes" rather than
"fields" ("It is the union, more or less, of a number of subject rich
indexes"). i.e.
Tolkien
is equivalent to some query of the form
index1 Tolkien or index2 Tolkien or index2 Tolkien or ...
My semantics for serverChoice and serverDefault are that they are
equivalent to
index Tolkien
Where that index is a single index which could be explicitly used in a
CQL query. From Ralph's description, you can't do an equivalent explicit
CQL query of the form
BasicIndex Tolkien
(it would give diagnostic index not known)
Matthew
|