gitter badge link and some akka leftovers

alstanchev · alstanchev · commit 1227fd5f452a · 2023-08-23T23:55:01.000+03:00
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 # pekko-persistence-inmemory
 
-[![Join the chat at https://app.gitter.im/#/room/#alstanchev/pekko-persistence-inmemory:gitter.im](https://badges.gitter.im/dnvriend/akka-persistence-inmemory.svg)](https://app.gitter.im/#/room/#alstanchev/pekko-persistence-inmemory:gitter.im?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Join the chat at https://app.gitter.im/#/room/#pekko-persistence-inmemory:gitter.im](https://badges.gitter.im/repo.svg)](https://app.gitter.im/#/room/#pekko-persistence-inmemory:gitter.im)
 [![Build Status](https://github.com/alstanchev/pekko-persistence-inmemory/actions/workflows/build.yml/badge.svg)](https://github.com/alstanchev/pekko-persistence-inmemory/actions/workflows/build.yml)
 [![Download](https://api.bintray.com/packages/dnvriend/maven/akka-persistence-inmemory/images/download.svg) ](https://s01.oss.sonatype.org)
 [![License](http://img.shields.io/:license-Apache%202-red.svg)](http://www.apache.org/licenses/LICENSE-2.0.txt)
@@ -330,302 +330,7 @@ inmemory-storage {
 }
 ```
 
-
-## Changelog
-### 2.5.15.2 (2019-06-28)
-  - Scala 2.11.x, 2.12.x, 2.13.x support
-  - Akka 2.5.15 -> 2.5.23
-
-### 2.4.20.1 (2019-06-28)
-  - Merged PR #59 "Pluggable storage" by [Beat Sager](https://github.com/BeatSager), thanks!
-
-### 2.5.15.1 (2018-09-09)
-  - Java 8 binary release
-
-### 2.5.15.0 (2018-08-29)
-  - Applied PR #50 "Fix for Akka Typed Persistence" by [Lukasz Sanek](https://github.com/s4nk), thanks!
-  - Java 10 binary release
-
-### 2.4.20.0 (2018-08-29)
-  - Merged PR #50 "Fix for Akka Typed Persistence" by [Lukasz Sanek](https://github.com/s4nk), thanks!
-  - Merged PR #52 "Provide nice Java API for clearing journal" by [Christopher Batey](https://github.com/chbatey), thanks!
-
-### 2.5.1.2 (2018-08-14)
-  - Merged PR #53 "Bump dependencies" by [Artsiom Miklushou](https://github.com/mikla), thanks!
-
-### 2.4.18.2 (2017-12-03)
-  - Merged PR #42 "Scala 2.12.4 support" by [sullis](https://github.com/sullis), thanks!
-
-### 2.5.1.1 (2017-05-23)
-  - Fix for issue #35 "no serializer for internal plugin messages"
-
-### 2.4.18.1 (2017-05-23)
-  - Fix for issue #35 "no serializer for internal plugin messages"
-
-### 2.5.1.0 (2017-05-03)
-  - Akka 2.5.0 -> 2.5.1
-
-### 2.4.18.0 (2017-05-03)
-  - Akka 2.4.17 -> 2.4.18
-  
-### 2.5.0.0 (2017-04-13)
-  - Support for Akka 2.5.0
-
-### 2.5.0.0-RC2 (2017-04-03)
-  - Support for Akka 2.5.0-RC2
-  
-### 2.5.0.0-RC1 (2017-03-21)
-  - Support for Akka 2.5.0-RC1
-  
-### 2.5.0.0-M2 (2017-02-24)
-  - Support for Akka 2.5-M2
-  - Changed to a simpler Time-based UUID generator.
-
-### 2.4.17.3 (2017-02-24)
-  - Changed to a simpler Time-based UUID generator.
-
-### 2.4.17.2 (2017-02-16)
-  - Fix for issue #33 'InMemoryReadJournal.eventsByPersistenceId returns deleted messages'
-
-### 2.5.0.1-M1 (2017-02-16)
-  - Fix for issue #33 'InMemoryReadJournal.eventsByPersistenceId returns deleted messages'
-  - Fix for PR #31 'eventsByTag including substrings of tag' by [jibbers42](https://github.com/jibbers42), thanks!
-  - Tags will be matched against the whole tag so tag 'foo' will be matched against 'foo' and not 'fo' or 'f' which was the previous behavior.
-
-### 2.4.17.1 (2017-02-12)
-  - Fix for PR #31 'eventsByTag including substrings of tag' by [jibbers42](https://github.com/jibbers42), thanks!
-  - Tags will be matched against the whole tag so tag 'foo' will be matched against 'foo' and not 'fo' or 'f' which was the previous behavior.
-
-### 2.4.17.0 (2017-02-11)
-  - Akka 2.4.16 -> 2.4.17
-
-### 2.4.16.0 (2017-01-29)
-  - New versioning scheme; now using the version of Akka with the akka-persistence-inmemory version appended to it, starting from `.0`
-  - Support for Akka 2.4.16
-  - Support akka 2.11.x and 2.12.x
-  - Changed how the `byTag` queries work, the requested offset is excluding, so if a materialized stream is created, when you ask for Sequence(2) for example, you will get Sequence(3) and so on
-    so this is for the use case when you store the lastest offset on the read side, you can just put that value in the query and the stream will continue with the next offset,
-    no need to manually do the plus-one operation.
-
-### 2.5.0.0-M1 (2017-01-29)
-  - New versioning scheme; now using the version of Akka with the akka-persistence-inmemory version appended to it, starting from `.0`
-  - Support for Akka 2.5-M1
-  - Support akka 2.11.x and 2.12.x
-  - You need Java 8 or higher
-  - Please read the [Akka 2.4 -> 2.5 Migration Guide](http://doc.org.apache.pekko.io/docs/akka/2.5-M1/project/migration-guide-2.4.x-2.5.x.html)
-  - Changed how the `byTag` queries work, the requested offset is excluding, so if a materialized stream is created, when you ask for Sequence(2) for example, you will get Sequence(3) and so on
-    so this is for the use case when you store the lastest offset on the read side, you can just put that value in the query and the stream will continue with the next offset,
-    no need to manually do the plus-one operation.
-
-### 1.3.18 (2016-12-21)
-  - Akka 2.4.14 -> 2.4.16
-
-### 1.3.17 (2016-12-08)
-  - Scala 2.12.0 -> 2.12.1
-
-### 1.3.16 (2016-11-22)
-  - Akka 2.4.13 -> 2.4.14
-
-### 1.3.15 (2016-11-19)
-  - Akka 2.4.12 -> 2.4.13
-
-### 1.3.14 (2016-11-03)
-  - cross scala 2.11.8 and 2.12.0 build
-
-### 1.3.13 (2016-11-01 - Birthday Edition!)
-  - Implemented support for the `org.apache.pekko.persistence.query.TimeBasedUUID`.
-  - You should set the __new__ configuration key `inmemory-read-journal.offset-mode = "uuid"`, defaults to `sequence`
-    to produce `EventEnvelope` that contain `TimeBasedUUID` offset fields.
-
-### 1.3.12 (2016-10-28)
-  - Akka 2.4.11 -> 2.4.12
-  - Support for the new queries `CurrentEventsByTagQuery2` and `EventsByTagQuery2`, please read the [akka-persistence-query](http://doc.org.apache.pekko.io/docs/akka/2.4.12/scala/persistence-query.html) documentation to see what has changed.
-  - The akka-persistence-inmemory plugin only supports the `org.apache.pekko.persistence.query.NoOffset` or `org.apache.pekko.persistence.query.Sequence` offset types.
-  - There is no support for the `org.apache.pekko.persistence.query.TimeBasedUUID` offset type. When used, akka-persistence-inmemory will throw an IllegalArgumentException.
-
-### 1.3.11 (2016-10-23)
-  - Scala 2.11.8 and 2.12.0-RC2 compatible
-
-### 1.3.10 (2016-09-30)
-  - Akka 2.4.10 -> 2.4.11
-
-### 1.3.9 (2016-09-22)
-  - Adapted version of PR #28 by [Yury Gribkov](https://github.com/ygree) - Fix bug: It doesn't adapt events read from journal, thanks!
-  - As event adapters are no first class citizins of akka-persistence-query (yet), a workaround based on the configuration of akka-persistence-cassandra
-    has been implemented in the inmemory journal based on the work of [Yury Gribkov](https://github.com/ygree). Basically, the query-journal will look for 
-    a __write-plugin__ entry in the __inmemory-read-journal__ configuration of your application.conf that must point to the _writePluginId_ that 
-    will write the events to the journal. That writePlugin has all event adapters configured and if applicable, those event adapters will be used to 
-    adapt the events from the data-model to the application-model effectively you should have application-model events in your _EventEnvelope_ if
-    configured correctly.
- - Removed the non-official and never-to-be-used bulk loading interface
-
-### 1.3.8 (2016-09-07)
-  - Akka 2.4.9 -> Akka 2.4.10
-
-### 1.3.7 (2016-08-21)
-  - Fix for EventsByPersistenceId should terminate when toSequenceNumber is reached as pointed out by [monktastic](https://github.com/monktastic), thanks!
-
-### 1.3.6 (2016-08-20)
-  - Akka 2.4.9-RC2 -> Akka 2.4.9
-
-### 1.3.6-RC2 (2016-08-06)
-  - Akka 2.4.9-RC1 -> 2.4.9-RC2
-
-### 1.3.6-RC1 (2016-08-03)
-  - Akka 2.4.8 -> 2.4.9-RC1
-
-### 1.3.5 (2016-07-23)
-  - Support for the __non-official__ bulk loading interface [org.apache.pekko.persistence.query.scaladsl.EventWriter](https://github.com/dnvriend/akka-persistence-query-writer/blob/master/src/main/scala/akka/persistence/query/scaladsl/EventWriter.scala)
-    added. I need this interface to load massive amounts of data, that will be processed by many actors, but initially I just want to create and store one or
-    more events belonging to an actor, that will handle the business rules eventually. Using actors or a shard region for that matter, just gives to much
-    actor life cycle overhead ie. too many calls to the data store. The `org.apache.pekko.persistence.query.scaladsl.EventWriter` interface is non-official and puts all
-    responsibility of ensuring the integrity of the journal on you. This means when some strange things are happening caused by wrong loading of the data,
-    and therefor breaking the integrity and ruleset of akka-persistence, all the responsibility on fixing it is on you, and not on the Akka team.
-
-### 1.3.4 (2016-07-17)
-  - Codacy code cleanup release.
-
-### 1.3.3 (2016-07-16)
-  - No need for Query Publishers with the new akka-streams API.
-
-### 1.3.2 (2016-07-09)
-  - Journal entry 'deleted' fixed, must be set manually.
-
-### 1.3.1 (2016-07-09)
-  - Akka 2.4.7 -> 2.4.8,
-  - Behavior of akka-persistence-query *byTag query should be up to spec,
-  - Refactored the inmemory plugin code base, should be more clean now.
-
-### 1.3.0 (2016-06-09)
-  - Removed the queries `eventsByPersistenceIdAndTag` and `currentEventsByPersistenceIdAndTag` as they are not supported by Akka natively and can be configured by filtering the event stream.
-  - Implemented true async queries using the polling strategy
-
-### 1.2.15 (2016-06-05)
-  - Akka 2.4.6 -> 2.4.7
-
-### 1.2.14 (2016-05-25)
-  - Fixed issue Unable to differentiate between persistence failures and serialization issues
-  - Akka 2.4.4 -> 2.4.6
-
-### 1.2.13 (2016-04-14)
-  - Akka 2.4.3 -> 2.4.4
-  
-### 1.2.12 (2016-04-01)
-  - Scala 2.11.7 -> 2.11.8
-  - Akka 2.4.2 -> 2.4.3
-
-### 1.2.11 (2016-03-18)
-  - Fixed issue on the query api where the offset on eventsByTag and eventsByPersistenceIdAndTag queries were not sequential  
-  
-### 1.2.10 (2016-03-17)
-  - Refactored the akka-persistence-query interfaces, integrated it back again in one jar, for jcenter deployment simplicity
-
-### 1.2.9 (2016-03-16)
-  - Added the appropriate Maven POM resources to be publishing to Bintray's JCenter
-
-### 1.2.8 (2016-03-03)
-  - Fix for propagating serialization errors to akka-persistence so that any error regarding the persistence of messages will be handled by the callback handler of the Persistent Actor; `onPersistFailure`.
-
-### 1.2.7 (2016-02-18)
-  - Better storage implementation for journal and snapshot
-
-### 1.2.6 (2016-02-17)
-  - Akka 2.4.2-RC3 -> 2.4.2
-
-### 1.2.5 (2016-02-13)
-  - akka-persistence-jdbc-query 1.0.0 -> 1.0.1
-
-### 1.2.4 (2016-02-13)
-  - Akka 2.4.2-RC2 -> 2.4.2-RC3
-
-### 1.2.3 (2016-02-08)
-  - Compatibility with Akka 2.4.2-RC2
-  - Refactored the akka-persistence-query extension interfaces to its own jar: `"com.github.dnvriend" %% "akka-persistence-jdbc-query" % "1.0.0"`
-
-### 1.2.2 (2016-01-30)
-  - Code is based on [akka-persistence-jdbc](https://github.com/dnvriend/akka-persistence-jdbc)
-  - Supports the following queries:
-    - `allPersistenceIds` and `currentPersistenceIds`
-    - `eventsByPersistenceId` and `currentEventsByPersistenceId`
-    - `eventsByTag` and `currentEventsByTag`
-    - `eventsByPersistenceIdAndTag` and `currentEventsByPersistenceIdAndTag`
-  
-### 1.2.1 (2016-01-28)
-  - Supports for the javadsl query API
-
-### 1.2.0 (2016-01-26)
-  - Compatibility with Akka 2.4.2-RC1 
-
-### 1.1.6 (2015-12-02)
- - Compatibility with Akka 2.4.1
- - Merged PR #17 [Evgeny Shepelyuk](https://github.com/eshepelyuk) Upgrade to AKKA 2.4.1, thanks!
-
-### 1.1.5 (2015-10-24)
- - Compatibility with Akka 2.4.0
- - Merged PR #13 [Evgeny Shepelyuk](https://github.com/eshepelyuk) HighestSequenceNo should be kept on message deletion, thanks!
- - Should be a fix for [Issue #13 - HighestSequenceNo should be kept on message deletion](https://github.com/dnvriend/akka-persistence-inmemory/issues/13) as per [Akka issue #18559](https://github.com/akka/akka/issues/18559) 
-
-### 1.1.4 (2015-10-17)
- - Compatibility with Akka 2.4.0
- - Merged PR #12 [Evgeny Shepelyuk](https://github.com/eshepelyuk) Live version of eventsByPersistenceId, thanks!
- 
-### 1.1.3 (2015-10-02)
- - Compatibility with Akka 2.4.0
- - Akka 2.4.0-RC3 -> 2.4.0
- 
-### 1.1.3-RC3 (2015-09-24)
- - Merged PR #10 [Evgeny Shepelyuk](https://github.com/eshepelyuk) Live version of allPersistenceIds, thanks!
- - Compatibility with Akka 2.4.0-RC3
- - Use the following library dependency: `"com.github.dnvriend" %% "akka-persistence-inmemory" % "1.1.3-RC3"` 
-
-### 1.1.1-RC3 (2015-09-19)
- - Merged Issue #9 [Evgeny Shepelyuk](https://github.com/eshepelyuk) Initial implemenation of Persistence Query for In Memory journal, thanks!
- - Compatibility with Akka 2.4.0-RC3
- - Use the following library dependency: `"com.github.dnvriend" %% "akka-persistence-inmemory" % "1.1.1-RC3"` 
-
-### 1.1.0-RC3 (2015-09-17)
- - Merged Issue #6 [Evgeny Shepelyuk](https://github.com/eshepelyuk) Conditional ability to perform full serialization while adding messages to journal, thanks!
- - Compatibility with Akka 2.4.0-RC3
- - Use the following library dependency: `"com.github.dnvriend" %% "akka-persistence-inmemory" % "1.1.0-RC3"` 
-
-### 1.1.0-RC2 (2015-09-05)
- - Compatibility with Akka 2.4.0-RC2
- - Use the following library dependency: `"com.github.dnvriend" %% "akka-persistence-inmemory" % "1.1.0-RC2"` 
-
-### 1.0.5 (2015-09-04)
- - Compatibilty with Akka 2.3.13
- - Akka 2.3.12 -> 2.3.13
-
-### 1.1.0-RC1 (2015-09-02)
- - Compatibility with Akka 2.4.0-RC1
- - Use the following library dependency: `"com.github.dnvriend" %% "akka-persistence-inmemory" % "1.1.0-RC1"` 
-   
-### 1.0.4 (2015-08-16)
- - Scala 2.11.6 -> 2.11.7
- - Akka 2.3.11 -> 2.3.12
- - Apache-2.0 license
-       
-### 1.0.3 (2015-05-25)
- - Merged Issue #2 [Sebastián Ortega](https://github.com/sortega) Regression: Fix corner case when persisted events are deleted, thanks!
- - Added test for the corner case issue #1 and #2
-
-### 1.0.2 (2015-05-20)
- - Refactored from the ConcurrentHashMap implementation to a pure Actor managed concurrency model
-
-### 1.0.1 (2015-05-16)
- - Some refactoring, fixed some misconceptions about the behavior of Scala Futures one year ago :)
- - Akka 2.3.6 -> 2.3.11
- - Scala 2.11.1 -> 2.11.6
- - Scala 2.10.4 -> 2.10.5
- - Merged Issue #1 [Sebastián Ortega](https://github.com/sortega) Fix corner case when persisted events are deleted, thanks!
-
-### 1.0.0 (2014-09-25)
- - Moved to bintray
-
-### 0.0.2 (2014-09-05)
- - Akka 2.3.4 -> 2.3.6
-
-### 0.0.1 (2014-08-19)
- - Initial Release
-
-Have fun!
+### 1.0.0 (2023-08-24)
+ - Fork from [dnvriend/akka-persistence-inmemory:2.5.15.2](https://github.com/dnvriend/akka-persistence-inmemory)
+ - Akka replaced with [Pekko 1.0.1](https://github.com/apache/incubator-pekko)
+ - Scala 2.12.x, 2.13.x, 3 support
diff --git a/documents/QueryConsumerArchitecture.md b/documents/QueryConsumerArchitecture.md
@@ -1,8 +1,8 @@
 # Query Consumer Refactor
-The akka persistence query api is based upon a push approach in where persisted events will be pushed
+The pekko persistence query api is based upon a push approach in where persisted events will be pushed
 downstream to any subscribers of the log. This rather naive approach has as a side effect that there has to
-be some kind of subscription management in akka-persistence. At the moment there is none available in 
-akka persistence and so the current design must change.
+be some kind of subscription management in pekko-persistence. At the moment there is none available in 
+pekko persistence and so the current design must change.
 
 # Looking at other log architectures
 There are other log architectures, for example [Apache Kafka](http://kafka.apache.org/), that use a clean separation
@@ -18,9 +18,9 @@ has the following responsibilities:
  * handing the response, which consists of a chunk of data beginning from the log position,
  * issuing the maximum number of messages the client can handle by means of a back pressure mechanism
  
-# Refactoring the akka persistence in-memory query clients
-When looking at the design of the Akka Persistence, the client api are also fully separate of the producer 
-of the log. When we copy the design of Kafka, the following changes to the design to the akka persistence
+# Refactoring the pekko persistence in-memory query clients
+When looking at the design of the Pekko Persistence, the client api are also fully separate of the producer 
+of the log. When we copy the design of Kafka, the following changes to the design to the pekko persistence
 in-memory query api clients can be made:
 
  * active clients that `pull` from the broker by issuing `fetch` requests,
@@ -29,7 +29,7 @@ in-memory query api clients can be made:
  * delivering the messages to any subscribers of the stream.
  
 This design places the responsibility of consuming the log and making sure that messages are send to any waiting subscribers 
-of the the log solely on the consumer API and decouples the producer from the consumer. The producer (here akka-persistence) 
+of the the log solely on the consumer API and decouples the producer from the consumer. The producer (here pekko-persistence) 
 must be changed because it does not have to take consumers into account. It has a single responsibility, batch writing messages
 to the log. 
 
