[
https://issues.apache.org/jira/browse/IGNITE-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov updated IGNITE-22204:
--------------------------------------
Description:
Patch IGNITE-16013 for AI-2 can not be applied for AI-3, because that patch
either (a) assumes that its inputs always returns
{noformat}
Sort(ordering=ord, offset=o, fetch=f)
>Scan
{noformat}
into
{noformat}
Limit (offset=o, fetch=f)
>Sort(ordering=ord, offset=o, fetch=f)
>>Scan
{noformat}
Which is not correct, because fetch and offset are applied twice.
was:
IGNITE-16013 incorrectly handles Sort(offset, fetch) transformation. It
transforms:
{noformat}
Sort(ordering=ord, offset=o, fetch=f)
>Scan
{noformat}
into
{noformat}
Limit (offset=o, fetch=f)
>Sort(ordering=ord, offset=o, fetch=f)
>>Scan
{noformat}
Which is not correct, because fetch and offset are applied twice.
> Sql. Incorrect Limit / Sort transformation
> ------------------------------------------
>
> Key: IGNITE-22204
> URL: https://issues.apache.org/jira/browse/IGNITE-22204
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0.0-beta2
> Reporter: Maksim Zhuravkov
> Assignee: Maksim Zhuravkov
> Priority: Critical
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Patch IGNITE-16013 for AI-2 can not be applied for AI-3, because that patch
> either (a) assumes that its inputs always returns
> {noformat}
> Sort(ordering=ord, offset=o, fetch=f)
> >Scan
> {noformat}
> into
> {noformat}
> Limit (offset=o, fetch=f)
> >Sort(ordering=ord, offset=o, fetch=f)
> >>Scan
> {noformat}
> Which is not correct, because fetch and offset are applied twice.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
