Peng-Lei commented on pull request #33339:
URL: https://github.com/apache/spark/pull/33339#issuecomment-908303107
> Due to the way to register a catalog right now (by configs), I feel it's a
bit hard to forbid invalid catalog names. If we do want to check the name,
shall we update the config setting logic, match the catalog registration
configs, and validate the catalog name there? so that we can fail it earlier.
@cloud-fan I test some testcase eg
```scala
sql("CREATE NAMESPACE IF NOT EXISTS testcat.testcat")
sql("DESCRIBE NAMESPACE testcat")
```
it will throw the exception.
As you said: spark try to use nameParts.head to load the catalog. So if we
use not a full-path and there is same name catalog, it will throw exception. Do
you think this need fix?
--
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]
