siddharthteotia commented on issue #9273: URL: https://github.com/apache/pinot/issues/9273#issuecomment-1226636894
Should we separately track resource / thread pool / execution scheduling issue or add it here ? Without that, this is unlikely to work for a mixed workload deployment where few new (join, subquery) queries go down the new engine (via option) with 2 or more stages whereas existing prod queries continue to run in the current engine with exactly 2 stages. For users who are purely interested in using the new engine, this is not that big of a problem. But since there is still a long way to go before fully adopting multi-stage engine for all queries, we need to solve this otherwise it will hinder usage / adoption of new engine's functionality for existing production users. -- 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
