All of my text below largely extends your question of syntax in a few
directions:
- What is the user experience of trying to run different statements
with this syntax?
- How do transactions interact with other Cassandra constructs?
- What are the execution semantics of these statements?
which I
On Wed, Oct 13, 2021 at 3:52 AM Henrik Ingo wrote:
> Aren't you actually pointing out a limitation in any "single shot"
> transactional algorithm? Including Accord itself, without any interactive
> part?
>
> What you are saying is that an Accord transaction is limited by the need
> for both the cl
On Tue, Oct 12, 2021 at 3:55 PM Henrik Ingo wrote:
> We define READ COMMITTED as "whatever is returned by Cassandra when
> executing the query (with QUORUM consistency)". In other words, this
> functionality doesn't require any changes to the storage engine or other
> fundamental changes to Cassan
Following up on my message yesterday as it looks like our replies may
> >> have crossed en route.
> >>>
> >>> Thanks for bumping your message from earlier in our discussion. I
> >> believe we have addressed most of these questions on the thread, in
>
