Inconsistent column references when EXPLAINing a fast path lookup #27154
Labels
A-CLUSTER
Topics related to the CLUSTER layer
A-compute
Area: compute
A-optimization
Area: query optimization and transformation
C-bug
Category: something is broken
What version of Materialize are you using?
be1a89b
What is the issue?
The following EXPLAINs should be printing the same thing, except for whether it's fast path, but they are showing different projections:
The inconsistency arises because the
ReadIndex
in the fast path case is actually a Join under the hood, which adds an extra column at the beginning, thus offsetting the column references.Also happening with Maps:
I'm not sure what's the best way to fix this:
ReadIndex
, e.g.,FastPathReadIndex
, and then we can just say thatFastPathReadIndex
emits the columns with an offset for unspecified reasons.The text was updated successfully, but these errors were encountered: