Thanks Scott. I will prioritize upgrading to 3.0.27 and will circle back if
this issue persists.
Jaydeep
On Tue, Sep 6, 2022 at 3:45 PM C. Scott Andreas
wrote:
> Hi Jaydeep,
>
> Thanks for reaching out and for bumping this thread.
>
> This is probably not the answer you’re after, but mentionin
Hi Jaydeep,Thanks for reaching out and for bumping this thread.This is probably not the answer you’re after, but mentioning as it may address the issue.C* 3.0.14 was released over five years ago, with many hundreds of important bug fixes landing since July 2017. These include fixes for issues that
Link to next episode:
Ep9 - Otavio Santana (Java Champion, open source dev)
https://drive.google.com/file/d/1NYk1zCyyHErkuyrJsFGannBx0NAYreea/view?usp=sharing
(You may have to download it to listen)
It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, September
If anyone has seen this issue and knows a fix, it would be a great help!
Thanks in advance.
Jaydeep
On Fri, Sep 2, 2022 at 1:56 PM Jaydeep Chovatia
wrote:
> Hi,
>
> We are running a production Cassandra version (3.0.14) with 256 tokens
> v-node configuration. Occasionally, we see that different
Hi Jacek,
Thanks for the great questions, they certainly all relate to things we
considered, so I hope I can answer them in a coherent way!
> will it be a replica group explicitly associated with each event
Some (but not all) events are explicitly associated with a replica group (or
more acc
Thanks all, going to merge those changes today!
> On Sep 2, 2022, at 5:47 AM, Josh McKenzie wrote:
>
> +1 to matching SQL. If we look at our population of users that are going to
> run into this, my intuition is that more of them will be familiar with SQL
> semantics than counters, so there's
So, looking more closely at your proposal I realise what you are trying to do.
The thing that threw me was your mention of lists and other collections. This
will likely not work as there is no index that is possible to define on a list
(or other collection) within a single sstable - a list is de
Hi Sam, this is a great idea and a really well described CEP!
I have some questions, perhaps they reflect my weak understanding, but
maybe you can answer:
Is it going to work so that each node reads the log individually and try to
catch up in a way that it applies a transition locally once the pre
> if that is standard for this project I will move the information there.
It is. I'd go to a CEP if you have something you think might be controversial
(due to design, size, whatever) and you want to get early consensus on before
going to deep on implementation.
I'm in favor of JIRA + DISCUSS (+
> On 5 Sep 2022, at 22:02, Henrik Ingo wrote:
>
> Mostly I just wanted to ack that at least someone read the doc (somewhat
> superficially sure, but some parts with thought...)
>
Thanks, it's a lot to digest, so we appreciate that people are working through
it.
> One pre-feature that we wo
10 matches
Mail list logo
