-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InMemory: Avoid server evaluating client functions #17050
Labels
area-in-memory
area-query
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
Comments
|
smitpatel
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Aug 23, 2019
Linking to #16963 |
Wrong issue. 🤦♂ |
smitpatel
removed
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Aug 23, 2019
When implementing this, also account for function with DbFunctionAttribute. They should go to server eval like they do on other databases. |
ajcvickers
added
the
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
label
Mar 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-in-memory
area-query
closed-out-of-scope
This is not something that will be fixed/implemented and the issue is closed.
Currently any function is server evaluatable for in memory. So we end up sending client functions to server also. That means we may be potentially causing memory leak.
We need to determine if inmemory should server eval client functions and if it does, how to avoid memory leaks.
The text was updated successfully, but these errors were encountered: