{"action":"created","issue":{"url":"https://api.github.com/repos/cockroachdb/cockroach/issues/7267","repository_url":"https://api.github.com/repos/cockroachdb/cockroach","labels_url":"https://api.github.com/repos/cockroachdb/cockroach/issues/7267/labels{/name}","comments_url":"https://api.github.com/repos/cockroachdb/cockroach/issues/7267/comments","events_url":"https://api.github.com/repos/cockroachdb/cockroach/issues/7267/events","html_url":"https://github.com/cockroachdb/cockroach/issues/7267","id":160631838,"number":7267,"title":"Add support to group all unique variants of a tuple in a range","user":{"login":"ddorian","id":1592898,"avatar_url":"https://avatars.githubusercontent.com/u/1592898?v=3","gravatar_id":"","url":"https://api.github.com/users/ddorian","html_url":"https://github.com/ddorian","followers_url":"https://api.github.com/users/ddorian/followers","following_url":"https://api.github.com/users/ddorian/following{/other_user}","gists_url":"https://api.github.com/users/ddorian/gists{/gist_id}","starred_url":"https://api.github.com/users/ddorian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ddorian/subscriptions","organizations_url":"https://api.github.com/users/ddorian/orgs","repos_url":"https://api.github.com/users/ddorian/repos","events_url":"https://api.github.com/users/ddorian/events{/privacy}","received_events_url":"https://api.github.com/users/ddorian/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cockroachdb/cockroach/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-06-16T10:44:58Z","updated_at":"2016-06-16T13:23:11Z","closed_at":null,"body":"Like in bigtable, where all key-values with the same ROW-KEY are in the same range. Something specifiable, like an index, that should always keep (col1,col2, etc) unique values in 1 range. This can and will be misused (like ~every feature). This is done so the app-developer can make queries where all the data will be guaranteed in 1 range/node.\r\n\r\nThis will(?) help with the performance since it will be used in cases where I know the data won't grow alot to be bigger than a range.\r\n\r\nOf course, this combination of columns can have only the columns of the primary-key and in the same order.\r\n\r\nMakes sense ?"},"comment":{"url":"https://api.github.com/repos/cockroachdb/cockroach/issues/comments/226483277","html_url":"https://github.com/cockroachdb/cockroach/issues/7267#issuecomment-226483277","issue_url":"https://api.github.com/repos/cockroachdb/cockroach/issues/7267","id":226483277,"user":{"login":"petermattis","id":6201335,"avatar_url":"https://avatars.githubusercontent.com/u/6201335?v=3","gravatar_id":"","url":"https://api.github.com/users/petermattis","html_url":"https://github.com/petermattis","followers_url":"https://api.github.com/users/petermattis/followers","following_url":"https://api.github.com/users/petermattis/following{/other_user}","gists_url":"https://api.github.com/users/petermattis/gists{/gist_id}","starred_url":"https://api.github.com/users/petermattis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/petermattis/subscriptions","organizations_url":"https://api.github.com/users/petermattis/orgs","repos_url":"https://api.github.com/users/petermattis/repos","events_url":"https://api.github.com/users/petermattis/events{/privacy}","received_events_url":"https://api.github.com/users/petermattis/received_events","type":"User","site_admin":false},"created_at":"2016-06-16T13:23:11Z","updated_at":"2016-06-16T13:23:11Z","body":"@ddorian Thanks for the clarification.\r\n\r\nThere is danger here in that a user might accidentally create very large ranges which are currently problematic. What should the system do if a range grows to multiple gigabytes because it can't be split? My instinct is that it would be better to figure out how to model the data as a single row and rely on rows being contained on a single range along with the (currently non-existent) row size limits.\r\n\r\nAnd I'm curious how much of a benefit this feature would provide. If your rows are contiguous, they are very likely on the same range. Multi-range operations are certainly slower than single-range operations, but not that much slower and if they are rare for your data set then they'll be lost in the noise.\r\n"}}
{"actor":{"display_login":"petermattis"}}