geyanggang commented on issue #9995: URL: https://github.com/apache/gravitino/issues/9995#issuecomment-3895438547
From the logs, a `NoSuchEntityException` was thrown, indicating that the entity corresponding to this column could not be found in the entityStore. This is the behavior of Gravitino core—it looks up the column entity in the metadata store, and since I am testing with BigQuery, the column metadata for BigQuery may not have been loaded or registered into the store yet. This is not an issue with the BigQuery catalog, nor is it entirely a UI issue. Rather, it is the behavior of Gravitino core’s policy/tag system: it requires that the metadata object already exists in the entity store before its tags or policies can be queried. Meanwhile, column information in the JDBC catalog is loaded on-demand from the remote source and is not pre-registered in the entity store. Although a 404 error occurred, the request eventually returned a 200, indicating that when the table details were loaded for the first time, Gravitino registered the column metadata into the store, and subsequent queries succeeded. In summary, this is a timing issue in Gravitino v2 UI + core: the UI concurrently requests the column’s tags/policies while fetching the table details, but the column entity has not yet been registered in the store at that point. -- 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]
