[
https://issues.apache.org/jira/browse/CASSANDRA-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425242#comment-17425242
]
Paulo Motta commented on CASSANDRA-16935:
-----------------------------------------
Thanks for the prompt response.
bq. It's never too late to bikeshed
It can definitely be too late to bikeshed - once a property name is out in the
wild, changing can be a nightmare. ;-)
bq. Happy to bikeshed the names, but doubt there are good options here.
I tend to prefer more meaningful names, if even they are bigger, versus cryptic
acronyms. How about v1_legacy_semantics or v1_no_read_read_linearizibility?
obviously this is just extreme bikeshedding so feel free to disregard.
> Use paxos_variant to specify Paxos behaviour
> --------------------------------------------
>
> Key: CASSANDRA-16935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16935
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Lightweight Transactions
> Reporter: Benedict Elliott Smith
> Priority: Normal
> Fix For: 4.x
>
>
> This patch introduces a config property for specifying the desired Paxos
> implementation and semantics. Initially, this will support only v1_norrl and
> v2, with “norrl” meaning “no read/read linearizability” i.e. supporting those
> use cases that need to restore prior performance, but only for read/read
> interactions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]