[
https://issues.apache.org/jira/browse/CASSANDRA-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610630#comment-14610630
]
Patrick McFadin commented on CASSANDRA-9200:
--------------------------------------------
bq. where sequence ids are reserved per session as I am proposing here per
coordinator.
The more I think of use cases and potential failure modes, I'm less -1 if we
enforce that sequences are never used in partition keys. That will eliminate a
ton of potential mis-use and disasters. I've been through sequence hell in
RDBMS land. Reset counters or buffer under-run can make for a long weekend.
If the proposal is to use a sequence with a partition key, then I'm at a loss
as to why that is useful.
> 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)
