[
https://issues.apache.org/jira/browse/CASSANDRA-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610387#comment-14610387
]
Jason Brown commented on CASSANDRA-9200:
----------------------------------------
I'd like to echo [~iamaleksey]'s sentiments. It feels like we're trying to jam
more RDBMS features into cassandra that don't fit very well in a distributed
system. When you say 'sequence', most RDBMS-expatriates will think it will
behave like Oracle/MySQL/SQLServer sequences, which it won't. Further, those
users will also expect to be able to list the rows in order by that seqeunce
value, as in "select * from foo order by bar_id desc" - which, for cassandra,
is a distributed range query, and we've done our damnedest to steer users away
from.
Gotta say I'm rather -1 on this in general, and that's before we start diving
into the failure cases.
> Sequences
> ---------
>
> Key: CASSANDRA-9200
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9200
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Robert Stupp
> Fix For: 3.x
>
>
> UUIDs are usually the right choice for surrogate keys, but sometimes
> application constraints dictate an increasing numeric value.
> We could do this by using LWT to reserve "blocks" of the sequence for each
> member of the cluster, which would eliminate paxos contention at the cost of
> not being strictly increasing.
> PostgreSQL syntax:
> http://www.postgresql.org/docs/9.4/static/sql-createsequence.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
