[
https://issues.apache.org/jira/browse/CASSANDRA-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610732#comment-14610732
]
Jason Brown commented on CASSANDRA-9200:
----------------------------------------
WRT to token/partition-scoping, this assumes that the tokens in a cluster are
constant/never change. We will run into data races/edge cases with cached
sequences being used as nodes are being added to the cluster, ranges being
moved, and so on. Perhaps with stronger consistency when cluster ownership
changes (CASSANDRA-9667), this can be worked alleviated.
bq. I reject this slippery slope argument
Selecting data by a monotonic value and asking that it be ordered is an
everyday common type of query that RDBMS users execute and expect with a
sequence. Otherwise, why bother to have a monotonic value? In that case what
you really want is uniqueness, which doesn't require monotonicity.
> 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)
