You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by "Jackie-Jiang (via GitHub)" <gi...@apache.org> on 2025/04/04 23:44:43 UTC
Re: [I] [multistage] Sub-Optimal Plan for IN Clause When Used with OR [pinot]
Jackie-Jiang commented on issue #15442:
URL: https://github.com/apache/pinot/issues/15442#issuecomment-2779908588
To debug this, you want to figure out if this is a bug from parser side, or optimizer side. IIRC, when combining `IN` with `OR`, Calcite directly parse the query into a quite weird join. The behavior should be fixed with Calcite `1.39` which we are trying to migrate to. cc @yashmayya @gortiz
--
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: commits-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org