{"action":"created","issue":{"url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/5","labels_url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/5/comments","events_url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/5/events","html_url":"https://github.com/okumin/akka-persistence-sql-async/issues/5","id":95704106,"number":5,"title":"Incompatible with Akka 2.4-M2 persistence API","user":{"login":"zackangelo","id":688990,"avatar_url":"https://avatars.githubusercontent.com/u/688990?v=3","gravatar_id":"","url":"https://api.github.com/users/zackangelo","html_url":"https://github.com/zackangelo","followers_url":"https://api.github.com/users/zackangelo/followers","following_url":"https://api.github.com/users/zackangelo/following{/other_user}","gists_url":"https://api.github.com/users/zackangelo/gists{/gist_id}","starred_url":"https://api.github.com/users/zackangelo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zackangelo/subscriptions","organizations_url":"https://api.github.com/users/zackangelo/orgs","repos_url":"https://api.github.com/users/zackangelo/repos","events_url":"https://api.github.com/users/zackangelo/events{/privacy}","received_events_url":"https://api.github.com/users/zackangelo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-07-17T17:28:21Z","updated_at":"2015-09-27T16:10:41Z","closed_at":null,"body":"Looks like some breaking changes were introduced in the 2.4-M2 persistence API. \r\n\r\nI have an updated branch that is compatible with 2.4-M2, but it will break binary compatibility with all the versions before that. How would you want to handle it? Publish a separate artifact?"},"comment":{"url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/comments/143573514","html_url":"https://github.com/okumin/akka-persistence-sql-async/issues/5#issuecomment-143573514","issue_url":"https://api.github.com/repos/okumin/akka-persistence-sql-async/issues/5","id":143573514,"user":{"login":"gavares","id":46012,"avatar_url":"https://avatars.githubusercontent.com/u/46012?v=3","gravatar_id":"","url":"https://api.github.com/users/gavares","html_url":"https://github.com/gavares","followers_url":"https://api.github.com/users/gavares/followers","following_url":"https://api.github.com/users/gavares/following{/other_user}","gists_url":"https://api.github.com/users/gavares/gists{/gist_id}","starred_url":"https://api.github.com/users/gavares/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gavares/subscriptions","organizations_url":"https://api.github.com/users/gavares/orgs","repos_url":"https://api.github.com/users/gavares/repos","events_url":"https://api.github.com/users/gavares/events{/privacy}","received_events_url":"https://api.github.com/users/gavares/received_events","type":"User","site_admin":false},"created_at":"2015-09-27T16:10:41Z","updated_at":"2015-09-27T16:10:41Z","body":"I did notice that events are *not* deleted from the tagged stream as you mentioned above. Their implementation seems to store tagged entries as just another event stream with a special prefix. Essentially, all tagged entries are written to the journal twice. Once with the original persistence_id and once with a special persistence_id for the tag. Deleting the original entry leaves the tagged version of the entry in place which is why they can achieve that behavior. This is certainly one possible implementation for sql-async and would actually have fewer moving parts in the end.\r\n\r\nInterestingly, the other query types don't have the same behavior. I'm not sure I understand why the behavior should be different for the different query types."}}