Regression: Code changes disabled support for expression indexes with COALESCE, CASE and DECODE [CORE3338] #3704
Assignees
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: Sean Leyne (seanleyne)summary: Some expression indexes with COALESCE, CASE and DECODE became inoperant => Regression: Code changes disabled support for expression indexes with COALESCE, CASE and DECODE |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @asfernandes
FB 2.5 introduced fixes related to COALESCE, CASE and DECODE expressions to not duplicate sub-expressions in BLR, which was slow and had some bugs. This has made with new blr_stmt_expr. But this new BLR verb turn to be very difficult to support, specially in the optimizer.
As a result of it, some bugs (CORE3310, for example) were introduced, and some expression indexes stopped to work.
An example of an expression index not working anymore: COMPUTED BY (COALESCE(N * 2, 0)).
The complete (for FB 3) solution for these problems is:
1) introduce new specialized BLR verbs for COALESCE and DECODE/CASE;
2) transform blr_stmt_expr to new nodes when parsing legacy BLR.
Solution for 2.5 still need more analysis.
Commits: bf77761
The text was updated successfully, but these errors were encountered: