zhangbutao commented on PR #6267: URL: https://github.com/apache/hive/pull/6267#issuecomment-4126289430
> This could make some confusing. For example, we declare a S3 catalog but the location is absent, then this catalog is created with a hdfs location, some databases without explicit location will be put under the hdfs, while some are on the cloud, it might be a problem if we use the FileSystem created by the catalog's properties to operate against these tables or databases. > > In HMS, we can enforce the location check when creating the catalog, if it's null and the catalog is native, then we should throw the exception. I understand what you mean. I think what we're discussing is more about usage habits. Before the catalog capability was available, Hive used databases as a way to isolate data, and when users created a Hive database, they could omit the location, in which case the database would use the default location. If users wanted to set a value different from the default catalog location, they could specify a specific location, such as an S3 location, when creating the catalog. This syntax of omiting the location is more flexible, and I think users might be more accustomed to the usage of having a default catalog location. I would also like to hear other folks' thoughts on the default catalog location. :) -- 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]
