Re: What is there in the commit-log

[Sreenivasulu Nallapati]

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?
DDL: DDL are logged as it is how we execute?



Thanks
Sreeni

On Mon, Feb 11, 2019 at 6:12 PM Horia Mocioi  wrote:

> 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/architecture/storage_engine.html#commitlog
>-
>
> https://stackoverflow.com/questions/34592948/what-is-the-purpose-of-cassandras-commit-log
>
>
> Regards,
> Horia
>
> On Mon, Feb 11, 2019 at 1:17 AM Sreenivasulu Nallapati <
> sreeni.nallap...@gmail.com> wrote:
>
> > Hi,
> >
> > I was wondering what is there in the commit-log. May be some examples
> with
> > below events
> > 1. Insert - only inserting data?
> > 2. Update - will it have before after change?
> > 3. Delete  - will it have before and after change?
> > 4. DDL - ?
> >
> > Please help me to understand
> >
> > Thanks
> > Sreeni
> >
>
>
> --
> 
>

[RELEASE] Apache Cassandra 2.1.21 released

[Michael Shuler]

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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.1 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.1.21
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.1.21
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 2.2.14 released

[Michael Shuler]

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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-2.2.14
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.14
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.0.18 released

[Michael Shuler]

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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.0.18
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.0.18
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[RELEASE] Apache Cassandra 3.11.4 released

[Michael Shuler]

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 and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 3.11 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-3.11.4
[2]: (NEWS.txt)
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-3.11.4
[3]: https://issues.apache.org/jira/browse/CASSANDRA

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.1.21

[Michael Shuler]

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, Michael Shuler wrote:
> *EOL* release for the 2.1 series. There will be no new releases from the
> 'cassandra-2.1' branch after this release.
> 
> 
> 
> I propose the following artifacts for release as 2.1.21.
> 
> sha1: 9bb75358dfdf1b9824f9a454e70ee2c02bc64a45
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.21-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1173/org/apache/cassandra/apache-cassandra/2.1.21/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1173/
> 
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.1.21-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.1.21-tentative
> 




signature.asc
Description: OpenPGP digital signature

Re: [VOTE PASSED] Release Apache Cassandra 2.2.14

[Michael Shuler]

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
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.14-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1172/org/apache/cassandra/apache-cassandra/2.2.14/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1172/
> 
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.14-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.14-tentative
> 




signature.asc
Description: OpenPGP digital signature

Re: [VOTE PASSED] Release Apache Cassandra 3.0.18

[Michael Shuler]

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
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.18-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1171/org/apache/cassandra/apache-cassandra/3.0.18/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1171/
> 
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.18-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.18-tentative
> 




signature.asc
Description: OpenPGP digital signature

Re: [VOTE PASSED] Release Apache Cassandra 3.11.4

[Michael Shuler]

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: fd47391aae13bcf4ee995abcde1b0e180372d193
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.4-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1170/org/apache/cassandra/apache-cassandra/3.11.4/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1170/
> 
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: CHANGES.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.4-tentative
> [2]: NEWS.txt:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.4-tentative
> 




signature.asc
Description: OpenPGP digital signature

Re: cqlsh tests and Python 3

[Ariel Weisberg]

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 (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. However this 
> would involve migrating cqlsh to Python 3. Does anybody have any concerns if 
> we move cqlsh to Python 3? Please note that Python 2 is EOL'd and will be 
> unsupported in about 10 months.
> So here are the options -
> 1. Leave cqlsh in Python 2.7 & nosetests. Just make sure they're running as 
> part of the build process.2. Move cqlsh to Python 3 & pytests.3. Leave cqlsh 
> in Python 2.7 but move to Pytests. This option doesn't really add much value 
> though.
> Thanks,
> Dinesh


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

cqlsh tests and Python 3

[dinesh.jo...@yahoo.com.INVALID]

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. However this would involve 
migrating cqlsh to Python 3. Does anybody have any concerns if we move cqlsh to 
Python 3? Please note that Python 2 is EOL'd and will be unsupported in about 
10 months.
So here are the options -
1. Leave cqlsh in Python 2.7 & nosetests. Just make sure they're running as 
part of the build process.2. Move cqlsh to Python 3 & pytests.3. Leave cqlsh in 
Python 2.7 but move to Pytests. This option doesn't really add much value 
though.
Thanks,
Dinesh

Re: What is there in the commit-log

[Horia Mocioi]

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/architecture/storage_engine.html#commitlog
   -
   
https://stackoverflow.com/questions/34592948/what-is-the-purpose-of-cassandras-commit-log


Regards,
Horia

On Mon, Feb 11, 2019 at 1:17 AM Sreenivasulu Nallapati <
sreeni.nallap...@gmail.com> wrote:

> Hi,
>
> I was wondering what is there in the commit-log. May be some examples with
> below events
> 1. Insert - only inserting data?
> 2. Update - will it have before after change?
> 3. Delete  - will it have before and after change?
> 4. DDL - ?
>
> Please help me to understand
>
> Thanks
> Sreeni
>


-- 

How to identify inserts/deletes/updates from CDC data

[Sreenivasulu Nallapati]

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 CommitLogReadHandler {

private static final Logger LOGGER =
LoggerFactory.getLogger(CustomCommitLogReadHandler.class);

private final String keyspace;
private final String table;

public CustomCommitLogReadHandler(Map configuration) {
keyspace = (String) YamlUtils.select(configuration,
"cassandra.keyspace");
table = (String) YamlUtils.select(configuration, "cassandra.table");
}

@Override
public void handleMutation(Mutation mutation, int size, int
entryLocation, CommitLogDescriptor descriptor) {
LOGGER.debug("Handle mutation started...");
for (PartitionUpdate partitionUpdate :
mutation.getPartitionUpdates()) {
process(partitionUpdate);
}
LOGGER.debug("Handle mutation finished...");
}

@SuppressWarnings("unchecked")
private void process(Partition partition) {
LOGGER.debug("Process method started...");
if (!partition.metadata().ksName.equals(keyspace)) {
LOGGER.debug("Keyspace should be '{}' but is '{}'.", keyspace,
partition.metadata().ksName);
return;
}
if (!partition.metadata().cfName.equals(table)) {
LOGGER.debug("Table should be '{} but is '{}'.", table,
partition.metadata().cfName);
return;
}
String key = getKey(partition);
JSONObject obj = new JSONObject();


Thanks
Sreeni