roryqi commented on PR #11156: URL: https://github.com/apache/gravitino/pull/11156#issuecomment-4507801078
> > Could u elaborate more about influence? Does it only influence the custom catalog? Custom catalog can't be used. This would be a breaking change. Could u avoid a breaking change? > > IRC has five backends: memory/jdbc/hive/rest/custom. Memory, jdbc and hive support table cache, while rest does not explicitly support it. Custom depends on the specific implementation. > > I have come up two solutions as follows: > > 1.Enable table cache by default. The document should specify which backends support table cache, and also indicate that if an unsupported backend is used, this configuration should be manually adjusted. > > 2.Disabled table cache by default. The configuration of the table cache remains the same as before, but it is necessary to add information in the documentation which backend supports table cache and which one doesn't. > > Which is better? @roryqi REST catalog is disable cached. Maybe we can disable the cache for the custom catalog, too. cc @jerryshao WDYT? -- 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]
