HEADS UP: 56.10 new size limit on notification queries

Get Help
1

Hey folks,

Metabase 56.10 introduces a size limit on query results used to generate a notification (email, etc.). The chart will fail to render and be replaced by a text message suggesting to reduce the query size. Large results get spooled to storage temporarily. On the plus side this should keep notification generation from sucking up too much memory (beyond GraalVM’s large appetite).

If you want the old behavior, set MB_NOTIFICATION_TEMP_FILE_SIZE_MAX_BYTES to zero, or you can set an explicit limit.

EDIT: Updated old behavior switch, thanks!

2 Likes
2

Thanks for the heads up @dwhitemv! One minor correction - to keep the old behavior, you should set MB_NOTIFICATION_TEMP_FILE_SIZE_MAX_BYTES to 0. The variable MB_ENFORCE_NOTIFICATION_TEMP_FILE_SIZE_LIMIT briefly existed in the PR that shipped this feature, but it did not make it to the release.

We strongly recommend against this though, since it can easily make Metabase go into a crash loop if it has a particularly expensive query that makes it run out of memory. Returning less data or a summary is the better option.