Re: ParDo requires its input to use KvCoder in order to use state and timers

If I am connecting the threads properly, you are trying to simulate triggering based on the size of buffered data, while you are using the type of message to route messages to one GCS location or another. Yes? On Tue, Feb 13, 2018 at 10:29 AM, Carlos Alonso wrote: > I have

Re: ParDo requires its input to use KvCoder in order to use state and timers

I have a question about this. My scenario is: * PubSub input with a timestampAttribute named doc_timestamp * Fixed windowing of one hour size. * Keys are an internal attribute of the messages (the type) * Messages of one particular type are way more frequent than the others, so it is likely a hot

Re: ParDo requires its input to use KvCoder in order to use state and timers

Ok, that makes a lot of sense. Thanks Kenneth! On Mon, Feb 12, 2018 at 5:41 PM Kenneth Knowles wrote: > Hi Carlos, > > You are quite correct that choosing the keys is important for work to be > evenly distributed. The reason you need to have a KvCoder is that state is >