yuqi1129 commented on issue #6612: URL: https://github.com/apache/gravitino/issues/6612#issuecomment-2710322780
> > This is the limitation of Hive Metastoreat present. For MySQL, Hive metastore only supports latin1 and does not support UTF8, see [issues.apache.org/jira/browse/HIVE-18083](https://issues.apache.org/jira/browse/HIVE-18083) > > Thanks [@yuqi1129](https://github.com/yuqi1129?rgh-link-date=2025-03-10T11%3A39%3A43.000Z) for the investigation. It looks be Hive's limitation, which is too old to fix it. I think Gravitino should persist such description fileds (using the same filed or create another filed, whatever) in our side, so that won't be restricted by underlying system. What do you think? [@jerryshao](https://github.com/jerryshao?rgh-link-date=2025-03-10T11%3A39%3A43.000Z) [@yuqi1129](https://github.com/yuqi1129?rgh-link-date=2025-03-10T11%3A39%3A43.000Z) Agree. https://github.com/apache/gravitino/commit/0e41493414fef118187c5e88c5ae75aca4bcb064 is just a temporary solution. To avoid such issues, we need to modify the current storage logic and place such fields in Graivinio storage, which we can control. -- 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]
