Plan enumeration for $or queries over clustered collections produces different plans when it is run over the $or branches vs. the whole query.

A clustered index scan can be created and used for individual branches, but it may not be created over the whole query, in which case only collection scan is created. 

In automaticCE plan ranker mode always use the subplanner if the collection is clustered.