Last tested: Sep 9, 2019
A PDT that has been created/modified in a user's dev mode has the following properties:
persist_for: 24 hours
regardless of what persistence is set.sql_trigger_value
will have an epoch timestamp on them in the hash (prod PDTs with a sql_trigger_value
will not).expires at: [timestamp]
where [timestamp] is 24 hours after the build completes (as it would show for a PDT with persist_for: 24 hours
).This content is subject to limited support.
UPDATE: As of 21.12, Dev Mode PDTs WILL show up in the Admin → PDTs panel: https://docs.looker.com/relnotes#pdt_development_mode_visibility
From what I have experienced in dev mode--
persist_for
will still be dropped after user-specified time (though I’ve only tested time that is less than 24 hours), whereas*_trigger
will behave as persist_for: 24 hours
I had issue with stale data in dev mode when I used *_trigger
but not when I used persist_for
, if I click “clear cache and refresh”; I do not have permission to manually rebuild PDTs