alexanderbianchi commented on issue #24:
URL: 
https://github.com/apache/datafusion-iceberg/issues/24#issuecomment-6987889851

   @alamb is there a reason that resolution hasn't been wired through the sql 
path? having to break up parsing + planning to traverse and resolve remote 
schema's isn't ideal.
   ```rust
       // Here is a query that selects data from a table in the remote catalog.
       let sql = "SELECT * from remote_schema.remote_table";
   
       // The `SessionContext::sql` interface is async, but it does not
       // support asynchronous access to catalogs, so we cannot register our 
schema provider
       // directly and the following query fails to find our table.
       let results = ctx.sql(sql).await;
       assert_eq!(
           results.unwrap_err().to_string(),
           "Error during planning: table 
'datafusion.remote_schema.remote_table' not found"
       );
   ```


-- 
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]

Reply via email to