Thanks for the proposal. I second Jordan that we need more abstraction in (1),
e.g. most cloud provider allow for disk snapshots and starting nodes from a
snapshot which would be a good mechanism if you find yourself there.
German
From: Jordan West
Sent: Sunday,
I am sympathetic to having a native fast instance migration solution as
this is a common operational recipe.
> It's valuable for Cassandra to have an ecosystem-native mechanism of
migrating data between physical/virtual instances outside the standard
streaming path. As Hari mentions, the current
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.30.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source an
On Thu, Apr 11, 2024 at 1:48 PM Brandon Williams
wrote:
> The vote will be open for 72 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s and no -1's.
The vote pas
+1
On Mon, Apr 15, 2024 at 8:03 AM Mick Semb Wever wrote:
>
>
>
>> Proposing the test build of Cassandra 3.11.17 for release.
>
>
>
>
>
> +1
>
>
> Checked
> - signing correct
> - checksums are correct
> - source artefact builds
> - binary artefact runs
> - debian package runs
> - debian repo ins
+1
On Mon, Apr 15, 2024 at 7:49 AM Mick Semb Wever wrote:
>
>
>
>> Proposing the test build of Cassandra 3.0.30 for release.
>>
>
>
> +1
>
>
> Checked
> - signing correct
> - checksums are correct
> - source artefact builds
> - binary artefact runs
> - debian package runs
> - debian repo install
> Proposing the test build of Cassandra 3.11.17 for release.
+1
Checked
- signing correct
- checksums are correct
- source artefact builds
- binary artefact runs
- debian package runs
- debian repo installs and runs
> Proposing the test build of Cassandra 3.0.30 for release.
>
+1
Checked
- signing correct
- checksums are correct
- source artefact builds
- binary artefact runs
- debian package runs
- debian repo installs and runs
We can open an issue with LEGAL to see what they say at least?
>>
>
>
> I will raise a LEGAL ticket.
>
> My question here is whether we have to go through the process of
> best-efforts to get approval to donate (transfer copyright), or whether we
> can honour the copyright on the prior work and mov
I think we might still have two functions.
The first one, format, as you just showed, which would copy the behaviour
in MySQL as closely as possible.
The second one would deal with sizes, like "format_size", which would
append size unit, as shown in the branch I posted.
WDYT?
Regards
On Thu, A
> tl,dr:
> - The AUTHORS lists everyone who ever made a commit (
> https://github.com/gocql/gocql/blob/master/AUTHORS)
> - The license is BSD-3 and explicitly says the copyright is owned by the
> authors (https://github.com/gocql/gocql/blob/master/LICENSE#L1)
> - We had a previous discussion about
11 matches
Mail list logo
