Where is model caching cron schedule in the new update

Bug reports
1

I can't find model cron update to update my model, I created a model but can't configure the cron setting?
where can I find it?

image
image1537×735 38.7 KB

image
image1531×780 35.1 KB

image
image1893×300 9.33 KB

2

From the "Caching" page where you see the default "every 6 hours" schedule - that drop down menu has a "Custom" option at the bottom. When you select it the Cron configuration box appears.

3

@leeloo
the caching page is not in v0.50.0

and you rolledback v0.50.0 and i can't install it again or downgrade metabase db

I need help please

i want to rollback or install v0.50.0

4

V50 was removed because there was a bug fix that needs to be corrected- V50.1 should be available later today. If you don't want to wait, the v50 jar file can still be directly downloaded even though the release itself was removed:

https://downloads.metabase.com/v0.50.0/metabase.jar

5

@leeloo
I'm using the docker, I want to rollback to v0.49.15

I installed v0.50.1 now and i can't see Model caching setting in the database or the cron schedule for it.

this is major thing for us.

what happened to Model caching?

6

@mmontaser I have a two fold answer for you here. These settings have been relocated to "Admin Settings -> Persistence -> Model Persistence" but the tab is not being displayed for OSS users right now (it is supposed to be visible).

There is a bug report in for this:

This was set to a priority 1 and it's been corrected - it will be out in v50.2 which is targeted to be released tomorrow.

7

thank you, i'll wait for this update

8

@leeloo

also Model persistence on/off is not in the database as well, the docs says it should be there

image
image1697×588 32.6 KB

9

In the version 50 docs it indicates that this is located on the persistence tab now:

10

@leeloo

I'm talking about this

image
image935×603 47.4 KB

11

@leeloo

the new version is working now but there is a weird error appearing in the logs, this is some of it because the error log is big

2024-06-13 08:14:38,312 ERROR query-processor.streaming :: Client closed connection prematurely
org.eclipse.jetty.io.EofException
        at org.eclipse.jetty.io.SocketChannelEndPoint.flush(SocketChannelEndPoint.java:116)
        at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422)
        at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:275)
        at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:254)
        at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:386)
        at org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:832)
12

Could you share the URL for that page?

13

@leeloo

it's the same link you shared under " Turn on model persistence for each database " section
but here it is again

14

@mmontaser Thank you for pointing that out! I completely missed it - let me check internally and get confirmation of what's supposed to be where and I'll come back with a clear answer.

On the other error you're seeing - are you on 50.2 or 50.3? What appDB are you using and what other database types are you connected to?

15

@mmontaser Ok - rounding back up on the model settings. The documentation is correct. It says:
"
Once you’ve turned on model persistence for your Metabase, you’ll need to set it up for each specific database, as Metabase will need to create a schema in your data warehouse to store the persisted models."

I just pulled 50.3 open source to confirm the behavior. The option on the individual databases does appear once Model Caching has been enabled from the "Model persistence" tab. Please let me know if I'm missing anything!