Hi guys. I had a question about Hive metastore an...
# troubleshooting
b
Hi guys. I had a question about Hive metastore and Hudi. In Flink SQL I create a catalog pointing to Hive metastore. I then create a database and a Hudi table. The Hudi table is created and Hive Metastore learns about the database and the table. The problem is that Hive does not know about the columns, only the table object. Is this by design or am I doing something wrong?
n
Did you use the
HoodieHiveCatalog
?
b
I didn’t…. Google doesnt return much on HoodieHiveCatalog?
n
b
ok trying that…
that seems to have helped, thanks.
Why does Hive metastore need to know about Hudi? It should be able to store the table metadata independent of the storage format no?
n
Great. Because HoodieHiveCatalog gets the Hudi metadata from HMS which is special to HMS.
b
I think if I’m creating a Hudi or an Iceberg table from Flink, with an external catalog HMS configured, I think we should be able to write the metadata thorugh the hive catalog. It seems to work like that but doesnt serialise the column names.
Maybe Im misunderstanding or maybe i hit a bug….
thanks for the help though. will continue….
I thought HMS was a service independent of the underlying storage formats
n
Different table format store different metadata of format itself.
The meta info isn’t unified.
b
would it be a similar pattern for iceberg tables?
n
No.
But this requires the storage meta unfied.