Roshan1299 commented on issue #10630: URL: https://github.com/apache/gravitino/issues/10630#issuecomment-4211155763
The PR was closed as @roryqi noted the current behavior is by design, entity store failure shouldn't block underlying catalog operations. However, the issue description mentions this leaves Gravitino in an inconsistent state where the table exists in the catalog but has no persisted metadata, and future cleanup runs won't discover it. Should the alternative approach be pursued instead — adding a fallback cleanup path or returning an explicit partial success/inconsistent-state result? @justinmclean @roryqi -- 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]
