Hi Michael, yes, the TCK is not published yet – it will be as part of the 2.3.5 release. If you would like to use it before that you can publishLocal from the akka-persistence-tck-experimental project from the release-2.3 branch.
Good luck with your plugin! On 11 August 2014 at 08:29:22, Michael Reardon (reard...@gmail.com) wrote: I looks like the TCK has not made it up to Maven-land yet, or is that just me? I'm been looking here: http://central.maven.org/maven2/com/typesafe/akka/ Incidentally, I've starting cobbling together a persistence plugin for CouchDB, so I too will be sorting out handling json with Akka Serializer. I've not noticed anyone using CouchDB with Akka Persistence yet, but if someone else has I'd love to hear about it. Thanks, Mike Reardon On Tuesday, August 5, 2014 3:54:56 AM UTC-7, Konrad Malawski wrote: By the way, implementing storage plugins is not so hard :-) Take a look at the docs: http://doc.akka.io/docs/akka/snapshot/scala/persistence.html#storage-plugins (I'm linking to snapshot here because in in 2.3.5 (coming soon) persistence includes an persistence plugin TCK – so you can verify if your plugin really works with this out of the box set of tests :-)) On Tue, Aug 5, 2014 at 12:51 PM, Konrad Malawski <kt...@typesafe.com> wrote: Hi Yann, since we provide user implementable Journal APIs to which we send PersistentRepr we (as in Akka) don't really have control over the format of how a journal plugin will decide to store this data. This is by design, since we want to be de-coupled from any database specifics in the APIs. In HBase I store a whole lot of data in the row key, an SQL journal would probably utilise separate columns for the persistenceId and the sequenceNr etc. It is up to the journal plugin to decide how the data will be fit into the database ("if you're mongo, just slap a json document into the collection and it'll work fine" – etc) – which is why my answer here is to implement a Journal plugin that would store the data in a way you see fit – just setting the serialiser won't be enough since the plugin may still do wrapping, and we can't force people to not do so, since perhaps it's exactly what they need. If your case is strong enough to really need full human readability, writing a small plugin shouldn't be to big of a price to pay :-) Related question: which database are you targeting? I hope you see my point and this helps in the long run! -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Konrad 'ktoso' Malawski hAkker @ typesafe http://akka.io -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
