mayank-pant opened a new issue, #19690: URL: https://github.com/apache/superset/issues/19690
### Motivation Different databases have different ways to optimize query. There are some changes which are forced from superset side which inhibits the query performance at the back end. One such optimization for clickhouse i have identified. ### Proposed Change Currently in bar-chart even when you have not selected LIMIT. LIMIT 50000<max value> still appears in the final query. If a table being queried uses a projection then clickhouse query optimizer gives inconsistent/wrong result for the query using both LIMIT and ORDER BY. I propose that if we do not select limit from the GUI, then it should not appear automatically in the final query. ### New or Changed Public Interfaces Dont have much idea about internals of superset but i have described my problem above. ### New dependencies n.a ### Migration Plan and Compatibility n.a ### Rejected Alternatives n.a -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
