[
https://issues.apache.org/jira/browse/IGNITE-21543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-21543:
--------------------------------------
Epic Link: IGNITE-21312
> Sql. Support arbitrary expressions values in partition pruning metadata.
> ------------------------------------------------------------------------
>
> Key: IGNITE-21543
> URL: https://issues.apache.org/jira/browse/IGNITE-21543
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Initial implementation of partition pruning metadata
> (https://issues.apache.org/jira/browse/IGNITE-21277) provided support of two
> classes of values: literals and dynamic parameters. This covers a lot of
> cases but it rejects trivial expressions such as:
> {code:java}
> SELECT * FROM t WHERE date_col = '2001-01-01'::DATE
> SELECT * FROM t WHERE uid_col = '0000-0000-0000-0000'::UUID
> {code}
> Let's allow arbitrary non-volatile (immutable and stable) * expressions as
> legal values for partition pruning metadata.
> - An expression is immutable if all its sub expressions are immutable.
> - An expression is stable if all its sub expressions are stable / or all
> expressions except some stable sub-expressions are immutable.
> - An expression is volatile if at least of its subexpressions is volatile.
> Immutable expressions: 1 + 2, ABS(42).
> Stable expressions: CURRENT_TIMESTAMP, CAST(CURRENT_TIMESTAMP AS VARCHAR).
> Volatile expressions: RANDOM and GEN_RANDOM_UUID
> [*] See documentation on function volatility in PostgreSQL -
> https://www.postgresql.org/docs/current/xfunc-volatility.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)