The join operation is tempting as a way to obtain the "current fold state" to which each message is folded into. I mean joining the source topic with folded topic as a way to have in the same function call both the current message to fold and the current state of the fold.But then each new "current fold state" computed by the function application above needs to be written (back) to that same table or topic. This seems to create a cycle. Did anyone encounter this or thought about how it would work? Does KafkaStreams have a way to identity cycles and create the necessary (needed) logic and yet avoid the infinite loop?
On Mon, 12 Oct 2020 at 17:39, Dumitru-Nicolae Marasoui < nicolae.maras...@kaluza.com> wrote: > Hello kafka community, > When I need to compute something that in regular programming in Scala or > Haskell would be a fold, how can it be done in Kafka-Streams? > > The join operation is tempting as a way to obtain the "current fold > state" to which each message is folded into. > > But then the results need to be written to that same table or topic. This > seems to create a cycle. > > Did anyone encounter this or thought about how it would work? > Thank you > > -- > > Dumitru-Nicolae Marasoui > > Software Engineer > > > 140-142, Kensington Church Street, London, W8 4BN > > w kaluza.com <https://www.kaluza.com/> > > LinkedIn <https://www.linkedin.com/company/kaluza> | Twitter > <https://twitter.com/Kaluza_tech> > > Kaluza Ltd. registered in England and Wales No. 08785057 > > VAT No. 100119879 > > Help save paper - do you need to print this email? > > -- Dumitru-Nicolae Marasoui Software Engineer 140-142, Kensington Church Street, London, W8 4BN w kaluza.com <https://www.kaluza.com/> LinkedIn <https://www.linkedin.com/company/kaluza> | Twitter <https://twitter.com/Kaluza_tech> Kaluza Ltd. registered in England and Wales No. 08785057 VAT No. 100119879 Help save paper - do you need to print this email?
