yuqi1129 commented on issue #9706: URL: https://github.com/apache/gravitino/issues/9706#issuecomment-4286787286
One thing we may need to note is that, currently, the Gravitino Lance REST service supports both `createTable`, `registerTable`, and `createEmptyTable`(deprecated in the later version). Only tables created by `createTable` can fetch the latest metadata and schema, whereas tables created by `registerTable` lack the necessary information, like S3 AKSK to handle it. This problem affects `Schema Source` and `Version Sync`. For tables that are only created or modified by Gravitino, it seems unnecessary to handle this problem. For tables that can be changed without Gravitino, Gravitino may lack information to update metadata, so we hesitate about it for a long time. How to handle synchronization problems for those tables only registered in Gravitino. > Configuration could enforce that all reads on external tables refresh and commit the schema. How can we guarantee that all changes without the Gravitino server can update versions in Gravitino? -- 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]
