That works. Thanks! Also, I should've done testConductor (instead of
TestConductor).
On Sat, Dec 26, 2015 at 9:11 AM, Patrik Nordwall
wrote:
> It must be done from the first node, where the concuctor runs. See akka
> source of multi-jvm tests for inspiration.
> fre 25 dec. 2015 kl. 18:08 skrev
Thanks a lot for your reply, Konrad – I have overlooked that overload of
GraphDSL.create() and your suggestion works great!
As a note, my user case is actually about *n *sinks that I need to combine
in this way. I am doing this via recursion right now, which again works
great.
– Kaspar
On Wed
It must be done from the first node, where the concuctor runs. See akka
source of multi-jvm tests for inspiration.
fre 25 dec. 2015 kl. 18:08 skrev :
> Hi hAkkers,
>
> I've been trying to figure out how to gracefully shutdown an actor system
> (or a jvm) in multi-jvm tests. The most naive way, whi
Yes
Some query journal plugins may have stronger guarantees. Consult the
documentation of the plugin that you are using.
lör 26 dec. 2015 kl. 15:42 skrev Jan-Terje Sørensen :
> Does that mean that if I depend on the order of different events they
> should all have the same persistentId?
>
>
> lør
Does that mean that if I depend on the order of different events they
should all have the same persistentId?
lørdag 26. desember 2015 13.15.05 UTC+1 skrev Patrik Nordwall følgende:
>
> Each PersistentActor instance has a unique persistenceId. A
> PersistentActor instance can persist different ty
Each PersistentActor instance has a unique persistenceId. A PersistentActor
instance can persist different types of events.
On Fri, Dec 25, 2015 at 3:24 PM, Jan-Terje Sørensen
wrote:
> Aha! I did not know that different events could have same persistenceId.
> Is the persistenceId the same as an
