bobtins edited a comment on issue #1877: URL: https://github.com/apache/arrow-datafusion/issues/1877#issuecomment-1065776134
I made a comment prematurely but I looked at code more and now I have some context. It looks like part of catalog/schema has already been implemented...and you're just trying to make it work the rest of the way. In the ExecutionContext there are already catalogs and schemas, which is why "show tables" works the way it does; however, to fully implement these, much more is needed: - table refs now have to be parsed into [catalog.[schema.]]table (you found that this is broken) - what if existing tables have "."? how do you escape? will you break things? - current catalog and schema need to be maintained in ExecutionContext - 1, 2, and 3-part names have to be interpreted correctly based on current context - add/update/delete of all these entities need to be implemented As I said in my previous rant, a lot of times you don't need this...and it can add extra complexity for developers to maintain, and for users to keep track of. How much would it take to finish this? Is there an alternate path? Just because something's in information_schema doesn't mean it has to be fully supported; it is just meant to be a cross-database metadata standard which maps down to existing functionality. Hope this perspective is helpful! -- 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]
