Daniel Packard
10/03/2024, 3:59 PMJacob Jona Fahlenkamp
10/03/2024, 10:44 PMDaniel Packard
10/04/2024, 12:54 AMDaniel Packard
10/04/2024, 12:54 AMJacob Jona Fahlenkamp
10/04/2024, 7:07 AMRalph Bartley
10/04/2024, 12:59 PMPedro Mázala
10/07/2024, 8:43 AMDaniel Packard
10/08/2024, 2:40 PMDo you want to serve this state to other applications? Or is this something as sanity check?"Serve to other applications" Just thinking it would be nice to expose state directly from flink, instead of populating some other service/cache via a kafka topic (or similar) What I've seen of the state processor API and queryable state, neither meets my needs without some backflips - so I'll probably just stand up a separate service and hydrate the state via kafka.
Pedro Mázala
10/11/2024, 9:54 AMso I'll probably just stand up a separate service and hydrate the state via kafka.I think this is the path indeed. Another con for me later was exposing flink internals to an service that would not need to know such thing.