[MDEV-12296] Cassandra Storage Engine v2, based on DataStax C++ driver Created: 2017-03-18  Updated: 2019-03-04  Resolved: 2019-03-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Cassandra
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: gsoc17, gsoc18


 Description   

MariaDB 10.1 had Cassandra Storage Engine which was developed for Cassandra 1.1.x. Back then, Cassandra provided a Thrift API, and that was what Cassandra-SE used.

Then, Cassandra 2.0 switched to using a different network protocol (and also changed the data model).

This task is to develop a Cassandra Storage Engine V2 using DataStax's C++ client library (https://github.com/datastax/cpp-driver).

See also: MDEV-8947 was a previous attempt to implement this engine. Unfortunately it didn't even produce a skeleton engine.



 Comments   
Comment by Matthew Galton [ 2017-03-19 ]

Hi I am Matthew Galton a MS Computer Science student and I will love to work on this task for GSoC 2017. I familiar with Cassandra and CQL. I have also studied the MariaDB storage engine API and how to implement handler and handlerton methods for a storage engine. I am currently studying CQL Grammar to point out the differences between it and SQL and so far SQL seems to be far more powerful than CQL whose grammar omits some clauses that are supported by SQL. I will be writing a proposal for this project and if there is a student already working on this I will move to another project.

Comment by Sachin Gwasikoti [ 2019-03-01 ]

Hi,
Q1)On a scale of 1-10. what would be the difficulty of this project? It was not completed in GSOC 2016 because of "no work planned on Cassandra SE". Q2) What all technologies are desired to know for this project

It would be of great help to recieve answers for my queries. Thanks in advance !

Comment by Sergei Golubchik [ 2019-03-04 ]

DataStax C++ driver uses a Apache 2.0 license that is incompatible with GPLv2. It's best to not to use it.

Generated at Thu Feb 08 07:56:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.