siddharthteotia commented on PR #13792: URL: https://github.com/apache/pinot/pull/13792#issuecomment-2285613778
> In https://github.com/apache/pinot/pull/9605, we introduced a change to not resolve non-aggregation group by queries into distinct query, if select clause is not exactly matching to group-by clause. This is a breaking change for our customer as existing query stopped working for us. To fix this, instead of throwing an exception, we can return original query and let pinot handle the query as group-by query. I think I still I don't understand why this is needed. I understand PR 9605 may have introduced a breaking change. But, isn't that the right thing to do SQL standard wise (In Pinot we have been trying to converge with Postgres) ? If there are no aggregation functions and the SELECT list expressions are not matching the GROUP BY expressions, then it can't be rewritten to DISTINCT and hence throw error. > To fix this, instead of throwing an exception, we can return original query and let pinot handle the query as group-by query. In your proposal, it is not intuitive to reason about results. What expressions are we going to project as part of user query response ? > I think this is standard SQL/Postgres compliant. I tried below queries in mysql and it works fine. What about Postgres ? -- 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]
