{"action":"created","issue":{"url":"https://api.github.com/repos/Gild/gild-api/issues/8","labels_url":"https://api.github.com/repos/Gild/gild-api/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/Gild/gild-api/issues/8/comments","events_url":"https://api.github.com/repos/Gild/gild-api/issues/8/events","html_url":"https://github.com/Gild/gild-api/issues/8","id":90527401,"number":8,"title":"Feeling about UUIDs?","user":{"login":"openmosix","id":209329,"avatar_url":"https://avatars.githubusercontent.com/u/209329?v=3","gravatar_id":"","url":"https://api.github.com/users/openmosix","html_url":"https://github.com/openmosix","followers_url":"https://api.github.com/users/openmosix/followers","following_url":"https://api.github.com/users/openmosix/following{/other_user}","gists_url":"https://api.github.com/users/openmosix/gists{/gist_id}","starred_url":"https://api.github.com/users/openmosix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/openmosix/subscriptions","organizations_url":"https://api.github.com/users/openmosix/orgs","repos_url":"https://api.github.com/users/openmosix/repos","events_url":"https://api.github.com/users/openmosix/events{/privacy}","received_events_url":"https://api.github.com/users/openmosix/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-06-24T00:39:03Z","updated_at":"2015-06-24T18:44:14Z","closed_at":null,"body":"How do we feel about moving out of the current object IDs in favor of UUIDs?\r\n\r\nhttps://github.com/Gild/gild-api#provide-resource-uuids\r\n\r\nI'm a +1 on this but the impact is remarkable. We could probably easily address though with a concern.\r\n\r\ncc: @taganaka @taganaka @tejo\r\n"},"comment":{"url":"https://api.github.com/repos/Gild/gild-api/issues/comments/114976869","html_url":"https://github.com/Gild/gild-api/issues/8#issuecomment-114976869","issue_url":"https://api.github.com/repos/Gild/gild-api/issues/8","id":114976869,"user":{"login":"stefanofontanelli","id":605760,"avatar_url":"https://avatars.githubusercontent.com/u/605760?v=3","gravatar_id":"","url":"https://api.github.com/users/stefanofontanelli","html_url":"https://github.com/stefanofontanelli","followers_url":"https://api.github.com/users/stefanofontanelli/followers","following_url":"https://api.github.com/users/stefanofontanelli/following{/other_user}","gists_url":"https://api.github.com/users/stefanofontanelli/gists{/gist_id}","starred_url":"https://api.github.com/users/stefanofontanelli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefanofontanelli/subscriptions","organizations_url":"https://api.github.com/users/stefanofontanelli/orgs","repos_url":"https://api.github.com/users/stefanofontanelli/repos","events_url":"https://api.github.com/users/stefanofontanelli/events{/privacy}","received_events_url":"https://api.github.com/users/stefanofontanelli/received_events","type":"User","site_admin":false},"created_at":"2015-06-24T18:44:14Z","updated_at":"2015-06-24T18:44:14Z","body":"From: http://docs.mongodb.org/manual/faq/developers/\n\n\n   -\n\n   Use the _id field explicitly.\n\n   MongoDB clients automatically add an _id field to each document and\n   generate a unique 12-byteObjectId\n   <http://docs.mongodb.org/manual/reference/glossary/#term-objectid> for\n   the _id field. Furthermore, MongoDB always indexes the _id field. For\n   smaller documents this may account for a significant amount of space.\n\n   To optimize storage use, users can specify a value for the _id field\n   explicitly when inserting documents into the collection. This strategy\n   allows applications to store a value in the _id field that would have\n   occupied space in another portion of the document.\n\n   You can store any value in the _id field, but because this value serves\n   as a primary key for documents in the collection, it must uniquely identify\n   them. If the field’s value is not unique, then it cannot serve as a primary\n   key as there would be collisions in the collection.\n\n\nMongoDB doesn't do any assumption of the value inside _id, I think the\nproblem is who wrote the code (he/she assumed that _id is ordered by time\nor is generated using time or whatever).\nI know if you use a random hash instead of the default value for _id you\nare going to lose the fact that you can sort by _id and get the data sorted\nby time.\n\n\nOn Wed, Jun 24, 2015 at 11:27 AM, Luca Bonmassar <notifications@github.com>\nwrote:\n\n> @tejo <https://github.com/tejo> the SecureRandom generates a random UUID.\n> However we do not check for uniqueness among the data resources, but only\n> on the single resource (from the code). While the collision chances are\n> extremely low, it might happen - correct?\n>\n> Also, I think we should investigate about overriding the Mongo _id - when\n> I looked at that for Distill, I decided to use a different field (uuid)\n> because it could create odd behaviors (the _id in Mongo is strongly\n> opinionated - it has properties of time sequence, etc - while the uuid is\n> randomic).\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/Gild/gild-api/issues/8#issuecomment-114973069>.\n>\n\n\n\n-- \n*Stefano Fontanelli*\nSenior Engineer of Data & Infrastructure | Gild, Inc.\n800-664-2366  | *cell *415-547-0722\n\n465 California Street, Suite 1200\nSan Francisco, CA 94104\nwww.gild.com\n"}}