Cassandra collections are a good way for handling tasks. Multiple elements can be stored in collections. There are limitations in Cassandra collections.
- Cassandra collection cannot store data more than 64KB.
- Keep a collection small to prevent the overhead of querying collection because entire collection needs to be traversed.
- If you store more than 64 KB data in the collection, only 64 KB will be able to query, it will result in loss of data.
There are three types of collections that Cassandra supports.
A Set stores group of elements that returns sorted elements when querying.
Here is the syntax of the Set collection that store multiple email addresses for the teacher.
Create table University.Teacher ( id int, Name text, Email set<text>, Primary key(id) );
Here is the snapshot where table "Teacher" is created with "Email" column as a collection.
Here is the snapshot where data is being inserted in the collection.
When the order of elements matters, the list is used.
Here is the snapshot where column courses of list type id added in table "Teacher."
Here is the snapshot where data is being inserted in column "coursenames".
Here is the snapshot that shows the current database state after insertion.
The map is a collection type that is used to store key value pairs. As its name implies that it maps one thing to another.
For example, if you want to save course name with its prerequisite course name, map collection can be used.
Here is the snapshot where map type is created for course name and its prerequisite course name.
Here is the snapshot where data is being inserted in map collection type.