I believe that was a design decision to ensure for clusters and such that state could not be modified on the fly (and thus possibly become inconsistent or alter what would be a normal provenance trace). Processors internally are responsible for maintaining the state they wish to keep, I don't think it's possible to tweak it in order to change the behavior of the processors.
Having said that, there are much more knowledgeable folks than me re: state management, hopefully they can clarify/correct my answer :) Regards, Matt > On Jul 28, 2016, at 3:21 PM, Peter Wicks (pwicks) <[email protected]> wrote: > > I'm using the QueryDatabaseTable processor. Frequently I would like to set > an initial state value for my columns max value, or I'd like to change the > value stored in State Management for that column, this comes up in > operational scenarios ("reload all data after this exact timestamp, that's > when everything went bad"). > > But in looking through the code, and even the rest API, I don't see any > options to set/modify a processes state. Am I missing something? Is there a > way to set initial values like I want? > > Regards, > Peter
