{"action":"created","issue":{"url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/370","repository_url":"https://api.github.com/repos/RBMHTechnology/eventuate","labels_url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/370/labels{/name}","comments_url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/370/comments","events_url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/370/events","html_url":"https://github.com/RBMHTechnology/eventuate/issues/370","id":196280777,"number":370,"title":"Allow EventsourcedProcessor to emit events with custom aggregation IDs","user":{"login":"danbim","id":300638,"avatar_url":"https://avatars.githubusercontent.com/u/300638?v=3","gravatar_id":"","url":"https://api.github.com/users/danbim","html_url":"https://github.com/danbim","followers_url":"https://api.github.com/users/danbim/followers","following_url":"https://api.github.com/users/danbim/following{/other_user}","gists_url":"https://api.github.com/users/danbim/gists{/gist_id}","starred_url":"https://api.github.com/users/danbim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danbim/subscriptions","organizations_url":"https://api.github.com/users/danbim/orgs","repos_url":"https://api.github.com/users/danbim/repos","events_url":"https://api.github.com/users/danbim/events{/privacy}","received_events_url":"https://api.github.com/users/danbim/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2016-12-18T15:15:03Z","updated_at":"2016-12-19T09:05:14Z","closed_at":null,"body":"My question on the Gitter channel:\r\n\r\n> I’m currently trying to create an EventsourcedProcessor that reads an event from event log A and writes a newly created event to event log B. I want the newly created event to be equipped with an aggregate ID. Unfortunately, AFAICS the event that will be sent to event log B can only contain the same “customDestinationAggregateIds” as the original event from event log A (which btw. doesn’t have and IMO shouldn’t have an aggregate ID).\r\nAm I right here that the API does not permit to realise such a scenario? Is this intended?\r\n\r\n... and @volkerstampa s answer\r\n\r\n> You are right, the current API does not permit to define custom aggregate ids when processing events in an EventsourcedProcessor, however I do not see a reason why this should not be possible. Feel free to open an issue for this. PRs are also welcome :grinning:."},"comment":{"url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/comments/267914633","html_url":"https://github.com/RBMHTechnology/eventuate/issues/370#issuecomment-267914633","issue_url":"https://api.github.com/repos/RBMHTechnology/eventuate/issues/370","id":267914633,"user":{"login":"krasserm","id":202907,"avatar_url":"https://avatars.githubusercontent.com/u/202907?v=3","gravatar_id":"","url":"https://api.github.com/users/krasserm","html_url":"https://github.com/krasserm","followers_url":"https://api.github.com/users/krasserm/followers","following_url":"https://api.github.com/users/krasserm/following{/other_user}","gists_url":"https://api.github.com/users/krasserm/gists{/gist_id}","starred_url":"https://api.github.com/users/krasserm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krasserm/subscriptions","organizations_url":"https://api.github.com/users/krasserm/orgs","repos_url":"https://api.github.com/users/krasserm/repos","events_url":"https://api.github.com/users/krasserm/events{/privacy}","received_events_url":"https://api.github.com/users/krasserm/received_events","type":"User","site_admin":false},"created_at":"2016-12-19T09:05:14Z","updated_at":"2016-12-19T09:05:14Z","body":"We already planned that for later versions of Eventuate that we are currently prototyping. There should be something like `EventMetadata` for that purpose. But this is a mid-term goal. For a short-term solution, the proposed one is a good compromise IMO."}}
{"actor":{"display_login":"krasserm"}}