The sbe traverseF primitive accepts a compareArray argument which is currently always false in SBE plans generated by Bonsai. We should make use of this to reduce the complexity of the SBE plans. It seems like there are a couple of options.

Possibly we could deduce during lowering what the value of compareArray should be. This would not require changing the meaning of PathTraverse in the filter context.

Alternatively, we could extend PathTraverse to accept a compareArray parameter. This would change the translation of some simple comparison queries (gt/lt/eq to array constant) and would in turn require changing index bounds building code. This may also require CE changes.