bowenli86 commented on issue #8390: [FLINK-12469][table] Clean up catalog API on default/current database URL: https://github.com/apache/flink/pull/8390#issuecomment-491097070 > default DB is most likely from configuration and it cannot be verified until a catalog is opened. This shouldn't be a problem as error will be reported later when the db is actually referenced. I wonder if we should verify its existence upon catalog opening and fail early if the db doesn't exist? The reason being that the default db cannot be changed at runtime. If SQL CLI users realize it's nonexistent in the later stage of their workflow, e.g. the default db name they put has a typo, they may have several options: 1) not use any feature related to default db, 2) reconfig and restart their clients and lost all their previous progress in memory, 3) create that db (not a good option for a typo name). None seems very user-friendly.
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
