Good day everyone. This is a 4.0 status email. One week since the last
update.
Jira board with 4.0 scope:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661
High level numbers by release phase:
Alpha: 1 (-0 from last update); It’s close, with Mick nearing end o
+1
On Mon, 14 Dec 2020 at 13:43, David Capwell
wrote:
> +1
>
> > On Dec 14, 2020, at 10:03 AM, Benjamin Lerer <
> benjamin.le...@datastax.com> wrote:
> >
> > Thank you for the feedback.
> > I propose to:
> >
> > - update the documentation to clarify the meaning of the fix version as
> > 'The
+1
> On Dec 14, 2020, at 10:03 AM, Benjamin Lerer
> wrote:
>
> Thank you for the feedback.
> I propose to:
>
> - update the documentation to clarify the meaning of the fix version as
> 'The version in which the item must be fixed' (e.g 4.0-beta if the ticket
> must be fixed in a beta rel
Thank you for the feedback.
I propose to:
- update the documentation to clarify the meaning of the fix version as
'The version in which the item must be fixed' (e.g 4.0-beta if the ticket
must be fixed in a beta release)
- create a 4.0-GA fix version and use it for the Quality testing
Hi all,
My customer wants to use Cassandra together with the CQRS pattern. This is to
say, they want to separate reads and writes to different tables, potentially in
different keyspace or database.
In my experience with relational databases I would set up a trigger on the
"write" table such th
I wanted to point out that beta version of the protocol was created [1]
only for development purposes:
> This is primarily useful for driver authors to start work against a new
protocol version when the work on that spans multiple releases. Users would
not generally be expected to utilize this fla
