The suspicious looking part are the Akka.Persistence.Query settings - looks like there is no Provider or connection string.
[11:13:40 ERR] An exception occured inside SelectAsync while executing Task. Supervision strategy: Stop
System.AggregateException: One or more errors occurred. (DataProvider '' not found.)
---> LinqToDB.LinqToDBException: DataProvider '' not found.
at LinqToDB.Data.DataConnection.GetDataProviderEx(String providerName, String connectionString)
at LinqToDB.Data.DataConnection.ConfigurationApplier.Apply(DataConnection dataConnection, ConnectionOptions options)
at LinqToDB.Data.ConnectionOptions.LinqToDB.Common.IApplicable<LinqToDB.Data.DataConnection>.Apply(DataConnection obj)
at LinqToDB.DataOptions.Apply(DataConnection dataConnection)
at LinqToDB.Data.DataConnection..ctor(DataOptions options)
at Akka.Persistence.Sql.Db.AkkaPersistenceDataConnectionFactory.<>c__DisplayClass4_0.<.ctor>b__0()
at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
--- End of stack trace from previous location ---
at System.Lazy`1.CreateValue()
at Akka.Persistence.Sql.Db.AkkaPersistenceDataConnectionFactory.GetConnection()
at Akka.Persistence.Sql.Extensions.ConnectionFactoryExtensions.ExecuteWithTransactionAsync[TState,T](AkkaPersistenceDataConnectionFactory factory, TState state, IsolationLevel level, CancellationToken token, Func`4 handler)
at Akka.Persistence.Sql.Query.Dao.BaseByteReadArrayJournalDao.<>c.<<JournalSequence>b__7_0>d.MoveNext()
--- End of inner exception stack trace ---
at Akka.Actor.PipeToSupport.PipeTo[T](Task`1 taskToPipe, ICanTell recipient, Boolean useConfigureAwait, IActorRef sender, Func`2 success, Func`2 failure)
This happens while attempting to run Akka.Persistence.Query to do projections.
Expected behavior
The non-default journal should be able to run queries normally.
// uses the same custom persistence id, but fully-qualified "akka.persistence.query.journal.ownershp"
var readJournal = Context.System.ReadJournalFor<SqlReadJournal>(OwnershipReadJournal.Identifier);;
Actual behavior
Crashes at startup
Additional context
Worth noting: this code also crashes when we have a default Akka.Persistence.Sql journal specified in addition to this custom journal. When we make our custom journal the default, everything works.
That a custom journal can run, including snapshots and Query, without a default journal being specified
That multiple custom journals can run independently - their own snapshot stores, metadata tables, event journals, and we need to test Akka.Persistence.Query in those scenarios too
Version Information Version of Akka.NET? latest Which Akka.NET Modules? Akka.Persistence.Sql
Describe the bug
When using the following configuration:
The HOCON ends up looking like this, which is slightly wrong / weird
The suspicious looking part are the Akka.Persistence.Query settings - looks like there is no Provider or connection string.
This happens while attempting to run Akka.Persistence.Query to do projections.
Expected behavior
The non-default journal should be able to run queries normally.
Actual behavior
Crashes at startup
Additional context
Worth noting: this code also crashes when we have a default Akka.Persistence.Sql journal specified in addition to this custom journal. When we make our custom journal the default, everything works.