itay livni
05/27/2020, 5:04 PMtarget
pattern for a task
that is called twice in the same flow but without mapping?
I currently am mucking around with this pattern below and thought of using tags to differentiate them.
duplicate_task_target = "{parameters[<A FLOW_PARAM>]}/{task_name}-{???}"
But that would mean keeping track of duplicate tasks ... which is burdensome when working on multiple flows that then get updated. Any other thoughts?
Aside: I think this goes to param based targeting mentioned in other threads.Chris White
05/27/2020, 5:07 PM{date:%strftime-%formatter}
with your favorite datetime formattercache_validator
/ cache_for
interfaceKyle Moon-Wright
05/27/2020, 5:14 PMitay livni
05/27/2020, 5:17 PMcache
arguments getting deprecated? https://docs.prefect.io/api/latest/core/task.html#task-2Chris White
05/27/2020, 5:34 PMResult
interface and off the task interface: https://github.com/PrefectHQ/prefect/issues/2619itay livni
05/27/2020, 5:35 PMChris White
05/27/2020, 5:36 PMitay livni
05/27/2020, 7:36 PMtask_run_id
🙂 and task_tags
. I am Still puzzled how to differentiate task runs and cache their unique results. With
cache_validator=partial_inputs_only(validate_on=['x', 'y']))
then previous result will be overwritten?Chris White
05/27/2020, 11:44 PMcache_validator
interface is currently completely independent from the target
interface, so it doesn’t write any data to disk. We’re hoping to unify the two in a more intuitive way but in the meantime I think using tags is the best way to go (for now).