I start to think in the problem of expanding our source partitions, it
looks like a stateless stream will handle the expansion properly after

In the case of a state-full then the problem seems different, first problem
is the changelog itself, the expected definition will miss match.

The second problem is the locality of the data, the results as new
partition will ben process in a task that dont have the associated state.

 Have someone design some work around or is there any additional
documentation I should look at?


Pegerto Fernandez


Check out our new blog, "Get your -aas in gear: Privatelink and PaaS 
democratisation on AWS" by Guy Richardson <https://goo.gl/CoRMqF> 

opencredo.com <http://www.opencredo.com/> . Twitter 
<https://twitter.com/OpenCredo> . LinkedIn 

OpenCredo Ltd -- Delivering Software Innovation

Registered Office:  5-11 Lavington Street, London, SE1 0NZ
Registered in UK. No 3943999

Reply via email to