[ https://issues.apache.org/jira/browse/IGNITE-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov updated IGNITE-22204: -------------------------------------- Summary: Sql. Set operation. Incorrect query transformation for a query with limit / offset that uses the same table (When RemoveSortInSubQuery is enabled) (was: Sql. Sort operator cannot use offset parameter) > Sql. Set operation. Incorrect query transformation for a query with limit / > offset that uses the same table (When RemoveSortInSubQuery is enabled) > -------------------------------------------------------------------------------------------------------------------------------------------------- > > 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 cannot be applied to AI-3, because that patch > assumes that Sort's input always returns data from a single source. > This assumption is not correct for the cases, when a query splits into > multiple fragments. > So transforming > {noformat} > Sort(ordering=ord, offset=o, fetch=f) > >Scan > {noformat} > into > {noformat} > Limit (offset=o, fetch=f) > >Sort(ordering=ord, fetch=f + o) > >>Scan > {noformat} > Is not a valid transformation when there is an Exchange operator between a > Limit and a Sort and should not be used. -- This message was sent by Atlassian Jira (v8.20.10#820010)