Kashif Faraz b6f8d7a1b3

Add query context param forceExpressionVirtualColumns to always use "expression"-type virtual columns in query plan (#12583) ...

SQL expressions such as those containing `MV_FILTER_ONLY` and `MV_FILTER_NONE`
are planned as specialized virtual columns instead of the default `expression`-type virtual columns.
This commit adds a new context parameter to force the `expression`-type virtual columns.

Changes
- Add query context param `forceExpressionVirtualColumns`
- Use context param to determine if specialized virtual columns should be used or not
- Moved some tests into `CalciteExplainQueryTest`

2022-06-22 15:33:50 +05:30

..

src

Add query context param forceExpressionVirtualColumns to always use "expression"-type virtual columns in query plan (#12583)

2022-06-22 15:33:50 +05:30

pom.xml

Bump up the versions (#12480)

2022-04-27 14:28:20 +05:30