Jackie-Jiang commented on PR #15610: URL: https://github.com/apache/pinot/pull/15610#issuecomment-2822476703
Let's hold off a little bit on this PR. In the long term we want to move to standard (PostgreSQL) behavior, so the question is how to provide smooth migration. Having a cluster config might not be enough for that purpose because we might need to have both behaviors supported at the same time so that user can switch from old query to new query. Using query option is also not ideal because if user can change the query and add a new option, they can directly switch to the new query. Regarding the mechanism in this PR, to reduce overhead of looking up config map within a map, we can init the operator table only when the config changes (via callback), then always use the same operator table at query time. -- 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-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
