Serialize as Json

[stuartsaltzman]

Is it possible to serialize the payload as Json using this persistence plugin? I think the plugin would need to honor any configured serialization plugins? Thanks!

[acjay]

I also would appreciate this ability

[acjay]

If I'm not mistaken, it seems like this plugin will use whatever the registered serializer is for a given type:

akka-persistence-sql-async/core/src/main/scala/akka/persistence/journal/sqlasync/ScalikeJDBCWriteJournal.scala

Lines 24 to 31 in ec6c977

	val result = messages.map { write =>
	write.payload.foldLeft(Try(Vector.empty[SQLSyntax])) { (acc, x) =>
	for {
	a <- acc
	bytes <- serialization.serialize(x)
	} yield a :+ sqls"(${keys(x.persistenceId)}, ${x.sequenceNr}, $bytes)"
	}
	}

Would this mean that one could register their own JSON serializers for the built-in Akka Persistence data structures in application.conf, as well as JSON serializers for their own event types, and everything would work?

I suppose one would also want to change the message types in the docs from BYTEA to JSON. You could use JSONB, but that seems less appropriate for most use cases. Both give you Postgres sugar for querying, but JSONB adds overhead in encoding, which doesn't carry its weight if planning to do the vast majority of querying via Akka Persistence.

[acjay]

Okay, I think I'm going to give this a shot, unless someone like @okumin with real knowledge reports back with a reason to think this wouldn't work, or might not be advisable. For my application, I'm expecting throughput to be on the order of an event per second max, so I'm not super concerned about latency at this point. The idea of being able to directly examine the underlying store and also to manage deployment of a familiar DB is really attractive for my purposes. I'll report back!

[okumin]

@stuartsaltzman @acjay
Excuse me for my late response.

You can serialize events or states by your custom serializers like the sample.

However, you may not store that as special types, e.g. JSONB.

Table schemas should be defined for each application considering its performance characteristic, so I'm planning to make table schemas customizable.