[jira] [Resolved] (IGNITE-23097) Sql. Invalid plan for IN with mix exact and approximate numerics

["Iurii Gerzhedovich (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Iurii Gerzhedovich resolved IGNITE-23097.
-----------------------------------------
    Resolution: Not A Problem

> Sql. Invalid plan for IN with mix exact and approximate numerics
> ----------------------------------------------------------------
>
>                 Key: IGNITE-23097
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23097
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Iurii Gerzhedovich
>            Priority: Major
>              Labels: ignite-3
>
> We can't get a plan for execution a query like 
> {code:java}
> SELECT c1 FROM T1 WHERE c1 IN (2.939049E38){code}
> Where IN contains approximate numeric (FLOAT or DOUBLE) and c1 - it's a column with any exact numeric type ( REAL, SMALLINT, INT, LONG, DECIMAL).
> For aforementioned query I get 
> {code:java}
> org.opentest4j.AssertionFailedError: Invalid plan (null): TableScan(table=[[PUBLIC, T1]], tableId=[1], filters=[=(CAST($t0):DOUBLE, 2.939049E38)], requiredColumns=[{0}]): rowcount = 15000.0, cumulative cost = IgniteCost [rowCount=100000.0, cpu=400000.0, memory=0.0, io=0.0, network=0.0], id = 32{code}
> See org.apache.ignite.internal.sql.engine.planner.datatypes.NumericInTypeCoercionTest#literals
> Let's investigate and fix it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)