<commit_before>Hecuba
======

There are few widely used Apache Cassandra clients and Hecuba is the abstraction over those clients so that you can switch between those easily.

Hecuba is currently in use in Wize Commerce and is being actively developed. 

Why Hecuba
==========
In greek mythology Hecuba (http://en.wikipedia.org/wiki/Hecuba) is the mother of Hector (http://en.wikipedia.org/wiki/Hector) and Cassandra (http://en.wikipedia.org/wiki/Cassandra) and grand mother of Asytanax (http://en.wikipedia.org/wiki/Astyanax). Whereas in NoSQL world Cassandra is a NoSQL storage, Hector and Astyanax are clients (Astyanax had initially spawned off of Hector) and Hecuba is the abstraction over Astyanax and Hector.    

Features
========

 - Hecuba supports all the regular methods to interact with Cassandra including gets, multigets, row and column slices, writes and deletes. 
 - Hecuba can be used to maintain your own secondary index without relying on Cassandra's implementation of secondary indexes. The main difference here is that Cassandra implementation tries to maintain the locality of the secondary indexes with the knowledge of the topology whereas hecuba implementation consider secondary index as another independent column family with pointers to the main table. 

 <commit_msg>testing.<commit_after>Hecuba
======

There are few widely used Apache Cassandra clients and Hecuba is the abstraction over those clients so that you can switch between those easily.

Hecuba is currently in use in Wize Commerce and is being actively developed. 

Why Hecuba
==========
In greek mythology Hecuba (http://en.wikipedia.org/wiki/Hecuba) is the mother of Hector (http://en.wikipedia.org/wiki/Hector) and Cassandra (http://en.wikipedia.org/wiki/Cassandra) and grand mother of Asytanax (http://en.wikipedia.org/wiki/Astyanax). Whereas in NoSQL world Cassandra is a NoSQL storage, Hector and Astyanax are clients (Astyanax had initially spawned off of Hector) and Hecuba is the abstraction over Astyanax and Hector.    

Features
========

 
- Hecuba supports all the regular methods to interact with Cassandra including gets, multigets, row and column slices, writes and deletes. 
- Hecuba can be used to maintain your own secondary index without relying on Cassandra's implementation of secondary indexes. The main difference here is that Cassandra implementation tries to maintain the locality of the secondary indexes with the knowledge of the topology whereas hecuba implementation consider secondary index as another independent column family with pointers to the main table. 

 
{'fraction_non_alphanumeric': 0.06141367323290846, 'fraction_numerical': 0.0, 'mean_word_length': 4.78125, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1234598', 'n_tokens_mistral': 672, 'n_tokens_neox': 623, 'n_words': 338}