This is an automated email from the ASF dual-hosted git repository.

fanningpj pushed a commit to branch 1.1.x
in repository https://gitbox.apache.org/repos/asf/pekko-persistence-jdbc.git


The following commit(s) were added to refs/heads/1.1.x by this push:
     new 0faba28  remove refs to akka-persistence-jdbc 5.0.0 (#374) (#376)
0faba28 is described below

commit 0faba288fba9cf30da3189b5fbba26dd54870c16
Author: PJ Fanning <[email protected]>
AuthorDate: Sat Nov 15 20:08:36 2025 +0100

    remove refs to akka-persistence-jdbc 5.0.0 (#374) (#376)
---
 core/src/main/resources/reference.conf                              | 6 +++---
 .../apache/pekko/persistence/jdbc/journal/dao/JournalTables.scala   | 1 -
 .../pekko/persistence/jdbc/query/CurrentEventsByTagTest.scala       | 2 +-
 docs/src/main/paradox/configuration.md                              | 3 ---
 4 files changed, 4 insertions(+), 8 deletions(-)

diff --git a/core/src/main/resources/reference.conf 
b/core/src/main/resources/reference.conf
index 3026393..2ee5877 100644
--- a/core/src/main/resources/reference.conf
+++ b/core/src/main/resources/reference.conf
@@ -107,7 +107,7 @@ jdbc-journal {
 
   tables {
 
-    # Only used in pre 5.0.0 Dao
+    # Only used in early version of Dao
     legacy_journal {
       tableName = "journal"
       schemaName = ""
@@ -164,8 +164,8 @@ jdbc-journal {
   # Only used for the legacy schema
   tagSeparator = ${pekko-persistence-jdbc.tagSeparator}
 
-  # If you have data from pre 5.0.0 use the legacy 
pekko.persistence.jdbc.journal.dao.legacy.ByteArrayJournalDao
-  # Dao. Migration to the new dao will be added in the future.
+  # If you have data from akka-peristence-jdbc pre 5.0.0 use the legacy
+  # pekko.persistence.jdbc.journal.dao.legacy.ByteArrayJournalDao Dao.
   dao = "org.apache.pekko.persistence.jdbc.journal.dao.DefaultJournalDao"
 
   # The size of the buffer used when queueing up events for batch writing. 
This number must be bigger then the number
diff --git 
a/core/src/main/scala/org/apache/pekko/persistence/jdbc/journal/dao/JournalTables.scala
 
b/core/src/main/scala/org/apache/pekko/persistence/jdbc/journal/dao/JournalTables.scala
index 382cb4e..06dd6fe 100644
--- 
a/core/src/main/scala/org/apache/pekko/persistence/jdbc/journal/dao/JournalTables.scala
+++ 
b/core/src/main/scala/org/apache/pekko/persistence/jdbc/journal/dao/JournalTables.scala
@@ -51,7 +51,6 @@ object JournalTables {
 }
 
 /**
- * For the schema added in 5.0.0
  * INTERNAL API
  */
 @InternalApi
diff --git 
a/core/src/test/scala/org/apache/pekko/persistence/jdbc/query/CurrentEventsByTagTest.scala
 
b/core/src/test/scala/org/apache/pekko/persistence/jdbc/query/CurrentEventsByTagTest.scala
index 129478e..e37bebc 100644
--- 
a/core/src/test/scala/org/apache/pekko/persistence/jdbc/query/CurrentEventsByTagTest.scala
+++ 
b/core/src/test/scala/org/apache/pekko/persistence/jdbc/query/CurrentEventsByTagTest.scala
@@ -195,7 +195,7 @@ abstract class CurrentEventsByTagTest(config: String) 
extends QueryTestSpec(conf
         // send a batch of 3 * 200
         val batch1 = sendMessagesWithTag(tag, 200)
         // Try to persist a large batch of events per actor. Some of these may 
be returned, but not all!
-        // Reduced for 5.0.0 as we can no longer do a batch insert due to the 
insert returning the ordering
+        // Reduced as we can no longer do a batch insert due to the insert 
returning the ordering
         // so trying to persist 1000s in a batch is slower
         val batch2 = sendMessagesWithTag(tag, 2000)
 
diff --git a/docs/src/main/paradox/configuration.md 
b/docs/src/main/paradox/configuration.md
index 061bef0..7a282ef 100644
--- a/docs/src/main/paradox/configuration.md
+++ b/docs/src/main/paradox/configuration.md
@@ -43,9 +43,6 @@ Java
 
 A `dropIfExists` variant is also available.
 
-**Note**: `SchemaUtils` was introduced in version 5.0.0.
-
-
 ## Reference Configuration
 
 pekko-persistence-jdbc provides the defaults as part of the 
@extref:[reference.conf](github:/core/src/main/resources/reference.conf). This 
file documents all the values which can be configured.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to