There is a lot of interest in ramp, but the dependency on requiring a
unique timestamp id is a bitch.
There is zero interest in committing and maintaining a more heavyweight
framework to get all the way to serializable cross-partition transactions.
On Fri, Aug 7, 2015 at 2:42 PM, Marek Lewandowsk
Hi Jonathan,
I haven’t heard about it before, but now I’ve read it and it indeed offers
something interesting. I’ve read blog post, paper and comments at Jira so I
need to digest it a bit and let it sink in. Thanks for letting me know about it.
Can you tell me something more about the status of
Have you seen RAMP transactions?
I think that's a much better fit for C* than fully linearizable operations
cross-partition.
https://issues.apache.org/jira/browse/CASSANDRA-7056
On Fri, Aug 7, 2015 at 7:56 AM, Marek Lewandowski <
marekmlewandow...@gmail.com> wrote:
> actually I have been also t
actually I have been also thinking about doing something like redundant
execution of transaction. So you have this *single active thing* that
executes transaction, but you can also have redundancy of form of other
_followers_ that try to execute same transactions (like a dry-run) and upon
detection
> On 07 Aug 2015, at 14:35, Marek Lewandowski
> wrote:
>
> In both of my ideas there
> is some central piece.
That’s the point - a single thing. A single thing IS a single-point-of-failure.
Sorry to reply that drastically: that’s an absolute no-go in C*. Every node
must be equal - no special
Hey Robert,
thanks for reply. Yes, you understood correctly although I don't think it
is quite necessary to provide full ACID support, concretely C could be
eventual. D is supported by Cassandra as long as they are replicas (I
think). I'd focus only on A and I for multiple statements, which still
Hey Marek,
you’ve put a lot of effort in your proposal and first of all: Thanks for that!
If I understood you right, your proposal is about full ACID support ; able to
handle multiple statements in a single transaction.
Cassandra is a database used in distributed environments - a few servers
s
Hello everyone,
*TL;DR;* I want to develop transactions (similar to those relational ones)
for Cassandra, I have some ideas and I'd like to hear your feedback.
*Long story short:* I want to develop prototype of solution that features
transactions spanning multiple Cassandra partitions resembling
