{"action":"created","issue":{"url":"https://api.github.com/repos/palantir/atlasdb/issues/69","labels_url":"https://api.github.com/repos/palantir/atlasdb/issues/69/labels{/name}","comments_url":"https://api.github.com/repos/palantir/atlasdb/issues/69/comments","events_url":"https://api.github.com/repos/palantir/atlasdb/issues/69/events","html_url":"https://github.com/palantir/atlasdb/issues/69","id":109516447,"number":69,"title":"Native UUID support","user":{"login":"leeavital","id":1482532,"avatar_url":"https://avatars.githubusercontent.com/u/1482532?v=3","gravatar_id":"","url":"https://api.github.com/users/leeavital","html_url":"https://github.com/leeavital","followers_url":"https://api.github.com/users/leeavital/followers","following_url":"https://api.github.com/users/leeavital/following{/other_user}","gists_url":"https://api.github.com/users/leeavital/gists{/gist_id}","starred_url":"https://api.github.com/users/leeavital/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/leeavital/subscriptions","organizations_url":"https://api.github.com/users/leeavital/orgs","repos_url":"https://api.github.com/users/leeavital/repos","events_url":"https://api.github.com/users/leeavital/events{/privacy}","received_events_url":"https://api.github.com/users/leeavital/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-10-02T15:35:03Z","updated_at":"2015-10-08T19:31:02Z","closed_at":null,"body":"Doing range scans with UUID row components is painful, because VAR_STRINGS shouldn't be range scanned. You either have to map UUID <=> (Long, Long) or UUID <=> (SHA256 hash)\r\n\r\nSince UUIDs partition evenly, it makes sense to add a native type that supports range scanning."},"comment":{"url":"https://api.github.com/repos/palantir/atlasdb/issues/comments/146663547","html_url":"https://github.com/palantir/atlasdb/issues/69#issuecomment-146663547","issue_url":"https://api.github.com/repos/palantir/atlasdb/issues/69","id":146663547,"user":{"login":"carrino","id":978139,"avatar_url":"https://avatars.githubusercontent.com/u/978139?v=3","gravatar_id":"","url":"https://api.github.com/users/carrino","html_url":"https://github.com/carrino","followers_url":"https://api.github.com/users/carrino/followers","following_url":"https://api.github.com/users/carrino/following{/other_user}","gists_url":"https://api.github.com/users/carrino/gists{/gist_id}","starred_url":"https://api.github.com/users/carrino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/carrino/subscriptions","organizations_url":"https://api.github.com/users/carrino/orgs","repos_url":"https://api.github.com/users/carrino/repos","events_url":"https://api.github.com/users/carrino/events{/privacy}","received_events_url":"https://api.github.com/users/carrino/received_events","type":"User","site_admin":false},"created_at":"2015-10-08T19:31:02Z","updated_at":"2015-10-08T19:31:02Z","body":"You could special case 16 and hand out a lot of subranges that start with\n16 to handle this case.  But that seems like overkill when you could just\ndo the (long, long) encoding, or we can just fix this bug directly like\nsha256.\n\nOn Thu, Oct 8, 2015 at 12:00 PM, Mark Elliot <notifications@github.com>\nwrote:\n\n> Do virtual nodes make this better?\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/palantir/atlasdb/issues/69#issuecomment-146655197>.\n>\n"}}