Values ¶
pdg.workItemCacheState.Clean
The work item’s cache is clean and it will cook from cache, assuming no upstream file changes occur before it cooks
pdg.workItemCacheState.CleanPending
The work item’s cache is clean, but a parent task may still invalidate it when it cooks by writing out a new file
pdg.workItemCacheState.DirtyAlways
The work item’s cache is always dirty because the node that contains it is configured to always cook, e.g. its Cache Mode is set to Write Files
pdg.workItemCacheState.DirtyEmpty
The work item’s cache is dirty because it has no output files, which means it always cooks
pdg.workItemCacheState.DirtyMissing
The work item’s cache is dirty because one or more of its expected output files don’t exist on disk
pdg.workItemCacheState.DirtyNew
The work item’s cache is dirty because one or more of its expected output files hasn’t been tracked by PDG before
pdg.workItemCacheState.DirtyStale
The work item’s cache is dirty because one or more upstream work items wrote new files during the active cook, which invalidates the cache state of downstream tasks.
pdg.workItemCacheState.Undefined
The work item doesn’t have a defined cache state, for example because its in a partitioner node which doesn’t perform cache handling