returnString commented on a change in pull request #9762:
URL: https://github.com/apache/arrow/pull/9762#discussion_r599063974



##########
File path: rust/datafusion/src/execution/context.rs
##########
@@ -512,6 +573,12 @@ pub struct ExecutionConfig {
     optimizers: Vec<Arc<dyn OptimizerRule + Send + Sync>>,
     /// Responsible for planning `LogicalPlan`s, and `ExecutionPlan`
     query_planner: Arc<dyn QueryPlanner + Send + Sync>,
+    /// Default catalog name for table resolution
+    default_catalog: String,

Review comment:
       This is a very good question!
   
   I think we could allow for that distinction, but it gets a little bit messy 
as we'd probably want to enforce that you can't have a default schema without a 
default catalog, so it'd look something like `Option<(String, Option<String>)>` 
(in fact, I had something like that for a bit before I settled on just using 
`datafusion.public` as the default setting for back-compat).
   
   I'm struggling to think of a use case though 🤔 Maybe if someone were 
developing a system where they wanted to _force_ users to fully qualify their 
table names?




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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to