bowenli86 commented on issue #8205: [FLINK-12238] [TABLE/SQL] Support database related operations in GenericHiveMetastoreCatalog and setup flink-connector-hive module URL: https://github.com/apache/flink/pull/8205#issuecomment-485187297 > I meant if user is using generic catalog, he/she's likely to expect to see only Flink DB/table when they call listDB/listTable. But if this generic catalog is based on a shared HMS instance, the call will return Hive DB/table as well. So I wonder whether it makes sense to do some filtering here. This is not an issue for Hive catalog, because if users use Hive catalog, they'll expect to access Hive metadata. I see. I agree on the ultimate goal to have better, more user-friendly hints in listDatabases/Tables/Views() for the generic catalog. Hive metastore API, however, only support filtering by name currently. Filtering by properties would read every whole meta-object, which is too excessive IMHO. In the first release, I think we can clearly document best practices to use the two catalogs together, e.g. use better naming conventions for Flink related objects like "flink-<db/table/view_name>" or setup better access control for users. I've added it to [FLINK-12275](https://issues.apache.org/jira/browse/FLINK-12275). If a better solution comes up later on, we'll definitely consider that. What do you think?
---------------------------------------------------------------- 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
