alamb commented on pull request #1072: URL: https://github.com/apache/arrow-datafusion/pull/1072#issuecomment-939439858
> In fact, I think we need to do the same thing for table provider as well, hardcoding table providers in protobuf leads to the same restriction. this is a good point at makes sense to me > I don't see a strong reason why we want to avoid referencing execution context during logical plan deserilization? Likewise, I don't see any reason to avoid referencing `ExecutionContext` during logical plan serialization. The only potential challenge I could see is if the same LogicalPlan could be run several times (with different `ExecutionContext`s) as might be done with with cached query plans in transaction processing systems. -- 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]
