There is currently no implementation of subplanning which works solely with CBR. Our current approach of only performing "whole query planning" and ranking plans with CBR may result in a large regression due to us failing to enumerate the best plan that the subplanner is able to find.

Until we have a mechanism for single table access planning to handle rooted $or in a cost based manner we should avoid performing join optimization for these queries.