icefury71 opened a new issue, #16687: URL: https://github.com/apache/pinot/issues/16687
In this PR: https://github.com/apache/pinot/pull/15350 we introduced an on the fly virtual column which ensures queries can continue running against a table, in the presence of schema evolution (eg: adding new columns to the schema) which would've failed before. However, for this to work, user still needs to invoke the reload operation. The new columns can then be queried successfully even though reload hasn't finished. There are several scenarios where we don't want to automatically reload a Pinot table (especially for large tables which might cause significant overhead on the server). What would be ideal is to have a new lightweight API (eg: schema refresh) which will ensure all the servers can get the latest schema (post schema evolution) without having to do a reload operation. CC @Jackie-Jiang @praveenc7 -- 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]
