{"action":"opened","issue":{"url":"https://api.github.com/repos/diego2013/CSR_Meteor/issues/138","labels_url":"https://api.github.com/repos/diego2013/CSR_Meteor/issues/138/labels{/name}","comments_url":"https://api.github.com/repos/diego2013/CSR_Meteor/issues/138/comments","events_url":"https://api.github.com/repos/diego2013/CSR_Meteor/issues/138/events","html_url":"https://github.com/diego2013/CSR_Meteor/issues/138","id":120247564,"number":138,"title":"Why do we have scenario ACK as separate document?","user":{"login":"diego2013","id":4389491,"avatar_url":"https://avatars.githubusercontent.com/u/4389491?v=3","gravatar_id":"","url":"https://api.github.com/users/diego2013","html_url":"https://github.com/diego2013","followers_url":"https://api.github.com/users/diego2013/followers","following_url":"https://api.github.com/users/diego2013/following{/other_user}","gists_url":"https://api.github.com/users/diego2013/gists{/gist_id}","starred_url":"https://api.github.com/users/diego2013/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diego2013/subscriptions","organizations_url":"https://api.github.com/users/diego2013/orgs","repos_url":"https://api.github.com/users/diego2013/repos","events_url":"https://api.github.com/users/diego2013/events{/privacy}","received_events_url":"https://api.github.com/users/diego2013/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/diego2013/CSR_Meteor/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-03T19:18:09Z","updated_at":"2015-12-03T19:18:09Z","closed_at":null,"body":"Why do we have a separate document for scenario AKCs? Right now these \"likes\" are persisted in a separate entity scenarioACK, which as ID the concatenation of scenario Id and user ID. The two other fields are the scenarioID and userID.\r\n\r\nI don't know what is the rationale for this against an embedded list of userIDs in the scenario Document. With the latter approach counting the number of ACKs would be the list size. Most expensive operation would be to check if a user ID is in the list O(n).\r\n\r\nWith the current approach we are creating a lot of documents. "}}