Hello Balaji <balaji.rajagopa...@olacabs.com>, Thanks for your reply. This confirms my earlier assumption that one of usual ways to do it is to hold and nurture the application-state in an external body; in your case: Redis.
So, I am trying to understand how does one share the handle to this external body amongst partitions: do I create a Connector to a Redis instance (referring to your case as an example) at the beginning of Flink application and share that amongst partitions using the _Broadcast_ mechanism? Obviously, the assumption is that the external body (Redis, in this case) will have to deal with concurrent access of elements of State, and updation etc. Operators simply call an API on Redis to store and retrieve elements from the application-state. Is my understanding correct? Yes, I am aware of the fresh creation of a Mapper for every tuple that comes in. In fact, this was the source of my original doubt before I posted the question. Thanks again for underscoring that. -- Nirmalya -- Software Technologist http://www.linkedin.com/in/nirmalyasengupta "If you have built castles in the air, your work need not be lost. That is where they should be. Now put the foundation under them."
