You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that the current connector supports the lookup function, but the implementation is to fully scan the table data and store it in the memory. If the table data is large, the memory usage of flink tm will be relatively high, and it may even be oom. I think we should support caching some data just like jdbc connector. Are there any plans to enhance the lookup function?
The text was updated successfully, but these errors were encountered:
I found that the current connector supports the lookup function, but the implementation is to fully scan the table data and store it in the memory. If the table data is large, the memory usage of flink tm will be relatively high, and it may even be oom. I think we should support caching some data just like jdbc connector. Are there any plans to enhance the lookup function?
The text was updated successfully, but these errors were encountered: