Open rsobies opened 2 weeks ago
We have discussed this idea internally too. If I would be so frank, I would like this to be a bit more extensive than just a flag.
Instead, I would like to be able to register a default Persistent Stream configuration that would be used for any SubscribingEventProcessor
.
Although just a flag will get the job done, I am confident the default config settings, that can be overridden when needed, will be requested soon after.
I have changed the type of this issue from Enhancement to Feature, is it would be new behavior we do not have in Axon Framework right now.
In case of taking this task on me, should I start from axon-4.10.x ?
In case of taking this task on me, should I start from axon-4.10.x ?
Given that we have somebody that will work on #3159 to introduce a new Serializer
, I think a 4.11.0 will happen in the future.
I simply don't think it makes sense to have such a massive feature like an AvroSerializer
in a patch release.
Further, given the nature of the changes you propose here, I think it would be fair to pair those up with a 4.11.0 release.
So, long story short, you can start from the master
branch instead of the axon-4.10.x
branch, assuming you want to pick this up right now, @rsobies!
I think i will be ale to start implentation in a week
Current Behaviour
In order to use persistent streams user need to configure manually each persistent stream per processing group
Wanted Behaviour
Let's introduce new property, when it is true AF should create all configuration of persistent streams for the user so the states of all processing groups would be keep on the axon server side. There would be no need to keep tracking tokens on the client side