Hi, Ivan, Sorry to reply late. Could you explain what state that you have to maintain in SystemConsumer, not in KV-store and checkpoint topics? Samza's SystemConsumer is designed as a "pump" to simply pump the messages in to Samza StreamTasks, where the main stateful process is executed. Why and what kind of state that you have to keep in the SystemConsumers?
As for the SystemConsumer's register method, the offset is for the input streams. It is to remember where the stream process should start reading the messages in the input topics. KafkaSystemConsumer actually implements the function reading messages from Kafka. The offset is used to initialize the consumer. -Yi On Thu, Dec 10, 2015 at 2:22 AM, <ivan.anti...@nordea.com> wrote: > Hello, > > 1) I need stateful SystemConsumer, similar to tasks functionality : > > https://samza.apache.org/learn/documentation/0.9/container/state-management.html > is there some reason why it is not implemented for SystemConsumer? > > > 2) SystemConsumer has *register* method, which receives stream offset > as parameter - is that offset for output streams. Why do I need that offset > then? If it is for input streams then which part actually reads messages > from kafka. Is there any sample code how to use that offsets? > > Thanks > Ivan > >
