[
https://issues.apache.org/jira/browse/CASSANDRA-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610896#comment-14610896
]
Sylvain Lebresne commented on CASSANDRA-9200:
---------------------------------------------
bq. It's expected that Cassandra will not provide you with all the
functionality you can possibly need. Having people roll their own is fine
sometimes, if the alternative is putting everything in C*. Especially features
that are bad architectural fit with Cassandra model.
I'm currently leaning towards that sentiment. Surely there isn't *that* many
user that re-implement IMAP :). More seriously, sequences are something you
should avoid if you can help it in a distributed system, and as far as I can
tell, at least the LWT based solution can be done client side, so it's not like
it's not doable by clients with Cassandra.
> 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)
