[IGNITE-18645] Sql. Type System. Reject plans with not matching dynamic parameters types during query validation.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0
• Component/s: sql
• Labels: calcite2-required calcite3-required ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Maksim Zhuravkov
• Created: 26/Jan/23 09:56
• Updated: 15/Oct/24 07:12

Description

Current implementation of dynamic parameters does not allow to reject plans that may fail runtime. Solution:

• dynamic parameters can be casted to appropriate types depending on the current context. If E1 with operand O1 expects a type T1 dynamic parameter D1 must be explicitly casted to T1 if it is possible. And if a cast is not possible a query must be rejected.
• in order to make type inference/type coercion possible we should use types of concrete values of dynamic parameters specified with a query.

This is a topic for discussion and investigation.

Issue Links

• relates to: IGNITE-18644 Sql. Type system. Types in predicate expressions may have unnecessary casts.
• relates to: IGNITE-18831 Sql. Dynamic parameters. Inferred types of dynamic parameters are not used by the execution runtime.