Re: [akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

Ah, thanks. That seems to confirm another suspicion of mine (though perhaps it's documented somewhere): that journal numbers should start at 1, not 0(?) Nothing else, I think. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

Re: [akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

It should terminate once it has arrived at or passed toSequenceNr. Otherwise I see no point in that parameter. toSeqNr=0 is an obvious boundary case, where it can terminate immediately. Anything else? /Patrik sön 21 aug. 2016 kl. 18:10 skrev Aditya Prasad : > On Sun, Aug

Re: [akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

On Sun, Aug 21, 2016 at 9:10 AM, Aditya Prasad wrote: > Thanks Patrick. > Sorry... thanks *Patrik*. > What are the more general conditions under which the stream should > terminate? > > I've come to appreciate the behavior that the stream terminates once it > has arrived at

Re: [akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

Thanks Patrick. What are the more general conditions under which the stream should terminate? I've come to appreciate the behavior that the stream terminates once it has arrived at or passed toSequenceNr. I wrote a tentative PR for the JDBC impl:

Re: [akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

I think it makes sense to complete the stream when it's know that there will be no events matching toSequenceNr. There is an effort to write a TCK for Persistence Query https://github.com/akka/akka/pull/20807 Unfortunately the PR has been inactive for a while now. It would be great if community

[akka-user] Re: leveldb readjournal eventsByPersistenceId hangs when toSequenceNr=0

Does anyone know the expected semantics of eventsByPersistenceId when toSequenceNr is less than or equal to the journal's latest version? In some impls & cases it completes the stream (which makes sense), and in others it does not (which is hard to work with). On Thursday, August 18, 2016 at