Code

Opened 4 years ago

Closed 4 years ago

#12617 closed (wontfix)

add support for Apache Cassandra

Reported by: flyinflash Owned by: nobody
Component: Database layer (models, ORM) Version: 1.2-alpha
Severity: Keywords: k/v, cassandra, key/value
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Apache Cassandra is a very good Key/Value store solution, please add support for it.

Thanks.

Attachments (0)

Change History (1)

comment:1 Changed 4 years ago by russellm

  • milestone 1.2 deleted
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

Specific support for Cassandra (or any other non-SQL tool) probably won't ever be in Django itself. It certainly isn't going to happen for 1.2.

However, we are interested in adding the interfaces necessary to allow a non-SQL backend to exist as an external project, much in the same way that Firebird and DB2 are externally supported SQL database backends.

There is a already a group of people working on a prototype for this interface. Depending on the progress they make, this interface might be added in Django 1.3. Most of the current efforts are targetting AppEngine, but any solution that gets to Django trunk will need to be agnostic of the needs of any specific storage engine. Having someone with Cassandra knowledge helping out would be beneficial. See NonSqlBackends for more details.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.