gruuya commented on issue #7292: URL: https://github.com/apache/arrow-datafusion/issues/7292#issuecomment-1682383307
> another possibility might be to add another argument to the `TableProvider::scan` True, but the main reason deferring the version resolution to the scan itself may be less favorable is that schemas can also evolve over different versions, and then we'd need to extend the `TableProvider::schema` method (and probably `TableProvider::statistics` or others). This means we'd also need to make any callers of these methods aware of what was the original version used in the query, which would mean a lot of new arguments all over the place. Hence, why having a separate `TableProvider` per version is better I think (and registering those ahead of time, when populating the `SessionContextProvider` for a given query). -- 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]
