[
https://issues.apache.org/jira/browse/IGNITE-18437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-18437:
----------------------------------------
Labels: calcite ignite-3 (was: )
> Sql. Fix row count estimate by limit with offset
> ------------------------------------------------
>
> Key: IGNITE-18437
> URL: https://issues.apache.org/jira/browse/IGNITE-18437
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: calcite, ignite-3
>
> This issue was already fixed in ai-2
> ([IGNITE-18363|https://github.com/apache/ignite/pull/10428/files#top]), need
> to adopt it a bit.
>
> Limit with offset can return negative estimated rows count, this will throw
> an assertion error if limit is used as input of another relational operator.
> For example:
> {code:java}
> CREATE TABLE t(id INT);
> INSERT INTO t VALUES (1), (2), (3);
> SELECT (SELECT id FROM t ORDER BY id LIMIT 1 OFFSET 10); \{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
