[ https://issues.apache.org/jira/browse/KYLIN-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weibin0516 updated KYLIN-4068: ------------------------------ Fix Version/s: v3.0.0-alpha2 Description: {code:sql} SELECT E_Name FROM Employees_China UNION SELECT E_Name FROM Employees_USA {code} will convert to {code:sql} SELECT E_Name FROM Employees_China UNION SELECT E_Name FROM Employees_USA LIMIT 50000 {code} This limit is not working on the result of union, but on SELECT E_Name FROM Employees_USA. We should use a more secure way to achieve the limit effect. was: {code:sql} SELECT E_Name FROM Employees_China UNION SELECT E_Name FROM Employees_USA {code} will convert to {code:sql} SELECT E_Name FROM Employees_China UNION SELECT E_Name FROM Employees_USA LIMIT 50000 {code} This limit is not working on the result of union, but on SELECT E_Name FROM Employees_USA. We should use a more secure way to achieve the limit effect. > Automatically add limit has bug > ------------------------------- > > Key: KYLIN-4068 > URL: https://issues.apache.org/jira/browse/KYLIN-4068 > Project: Kylin > Issue Type: Bug > Components: Query Engine > Affects Versions: v2.6.2 > Reporter: weibin0516 > Assignee: weibin0516 > Priority: Major > Fix For: v3.0.0-alpha2 > > > {code:sql} > SELECT E_Name FROM Employees_China > UNION > SELECT E_Name FROM Employees_USA > {code} > will convert to > {code:sql} > SELECT E_Name FROM Employees_China > UNION > SELECT E_Name FROM Employees_USA > LIMIT 50000 > {code} > This limit is not working on the result of union, but on SELECT E_Name FROM > Employees_USA. > We should use a more secure way to achieve the limit effect. -- This message was sent by Atlassian Jira (v8.3.2#803003)