Hi Horia,
Thanks for the response. I was looking in terms of how commit-log will
store each operation internally.
My queries are, for each one of the below query how commit log entry will
look like
Insert/Update/Delete: will there be insert/update/delete statement and
values in the commit-log?
DD
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.21.
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 a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.14.
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 a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.18.
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 a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.4.
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 a
I count 7 binding +1's, 1 non-binding +1 vote, and no others, so this
vote passes. I'll publish the artifacts as soon as I can.
Thanks for the discussion on support life of the 2.1 branch. I will not
be making any changes to the notes on the download page.
Kind regards,
Michael
On 2/2/19 6:32 PM
With 7 binding +1 votes, 2 non-binding +1, and no others, this vote
passed. I'll upload the artifacts as soon as possible.
Kind regards,
Michael
On 2/2/19 6:32 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.2.14.
>
> sha1: af91658353ba601fc8cd08627e8d36bac62e936a
With 8 binding +1 votes, 3 non-binding +1's, and no other votes, this
vote passed. I'll publish artifacts as soon as I can.
Kind regards,
Michael
On 2/2/19 6:32 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.18.
>
> sha1: edd52cef50a6242609a20d0d84c8eb74c580035e
I count 8 binding +1 votes, 3 non-binding +1's, and no other votes, so
this vote passes. I'll get the artifacts published as soon as I can.
Kind regards,
Michael
On 2/2/19 6:31 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.11.4.
>
> sha1: fd47391aae13bcf4ee995abc
Hi,
Do you mean Python 2/3 compatibility?
This has been discussed earlier and I think that being compatible with both is
an easier sell.
Ariel
> On Feb 11, 2019, at 1:24 PM, dinesh.jo...@yahoo.com.INVALID
> wrote:
>
> Hey all,
> We've gotten the cqlsh tests running in the Cassandra repo (t
Hey all,
We've gotten the cqlsh tests running in the Cassandra repo (these are distinct
from the cqlsh tests in dtests repo). They're in Python 2.7 and using the
nosetests. We'd like to make them consistent with the rest of the tests which
means moving them to Python 3 & Pytest framework. Howeve
Hello Sreeni,
When a write occurs to Cassandra, the operations is first stored in the
commit log. Write operation means: insert/update, delete or column family
change.
You can check the following explanations regarding the use of commit logs.
-
http://cassandra.apache.org/doc/latest/archi
Hi,
I am parsing the commit log files and I could not able to segregate the
inserts/deletes/updates from the mutations. Is there any way that we can
identify the event that is executed from commit logs?
Here is the partial code:
public class CustomCommitLogReadHandler implements CommitLogReadHand
13 matches
Mail list logo
