PDT cache being dropped after PR merge

[Lucas_Abreu]

Hi, there

we have noticed, couple of while ago actually, that everytime that a PR that affect a PDT’s SQL is merged, the cache of this PDT, and any other relying on it, is dropped and a new PDT build is started in the backend. In the meanwhile, end user won’t have access to the PDT data.

We were wondering if there’s anyway to prevent this behavior, namely, to keep the old cache for end users in production while the new PDT rebuilds in the background and then replace the old cache with the new one.

P.S.: we have a sorta workaround on this: we rebuilt the PDT’s that will be affected by the PR in our local branch, then push it to production as soon it builds, the problem are several as you might expect.

Any help is appreciated on this.

Tks,
Lucas

[kevin1]

Hi Lucas,

We are currently scoping this issue and planning to address it later this year. We agree this needs to be fixed!

Best,
Kevin Marr
Product Manager @ Looker

[Lucas_Abreu]

Hi, Kevin

do you have any idea about when this might happen?

Tks in advance,
Lucas