Practical Cassandra:A Developer's Approach

是 否 +2 论坛币

k人 参与回答

经管之家送您一份

应届毕业生专属福利!

求职就业群

赵安豆老师微信：zhaoandou666

经管之家联合CDA

送您一个全额奖学金名额~ !

立即领取

感谢您参与论坛问题回答

经管之家送您两个论坛币！

+2 论坛币

Practical Cassandra

A Developer's Approach

Book Description
Practical Cassandra is the first hands-on developer's guide to building Cassandra systems and applications that deliver breakthrough speed, scalability, reliability, and performance. Fully up to date, it reflects the latest versions of Cassandra–including Cassandra Query Language (CQL), which dramatically lowers the learning curve for Cassandra developers.

Pioneering Cassandra developers and Datastax MVPs Russell Bradberry and Eric Lubow walk you through every step of building a real production application that can store enormous amounts of structured, semi-structured, and unstructured data. Drawing on their exceptional expertise, Bradberry and Lubow share practical insights into issues ranging from querying to deployment, management, maintenance, monitoring, and troubleshooting.

Book Details

• Publisher:        Addison-Wesley
• By:        Russell Bradberry, Eric Lubow
• ISBN:        978-0-321-93394-2
• Year:        2013
• Pages:        208
• Language:        English
• File size:        5.1 MB
• File format:        PDF
• Download:     

  本帖隐藏的内容

  Practical Cassandra.pdf (4.82 MB, 需要: 20 个论坛币)

  2015-4-17 08:50:40 上传

  
  需要: 20 个论坛币  [购买]
  
  
  

扫码加我 拉你入群

请注明：姓名-公司-职位

以便审核进群资格，未注明则拒绝

分享0 收藏1 回帖

关键词：developer Practical Approach practic Develop developer including learning building deliver

1. Listing 3.4 Example of Cassandra Data Model for Log Storage (Copy of RDBMS)
   
2. 
   
3. CREATE TABLE events (
   
4. id UUID PRIMARY KEY,
   
5. time TIMESTAMP,
   
6. event_type TEXT,
   
7. data text
   
8. );

复制代码

We can solve some of the issues here with indexes; however, the code would not be as performant as it could be. Let’s say you would like to get all events for a particular hour. We can easily add an index to the time field, but this will cause excessive load, as every event will need to be pulled from different rows scattered about the cluster.

To compensate for this, since we know the hour we want ahead of time, we can key off that, and by using dynamic tables in Cassandra, we can ensure that every event for that particular hour exists, physically, on the same row. When you specify multiple fields in the PRIMARY KEY, Cassandra will key off the first field and every subsequent field will be a part of the column name. In Listing 3.5, we restructure the code to store fields by hour in the table to make hourly lookups of events easier.