New row cache options proposition

[Perez Felipe <fe...@thalesgroup.com>]

Hi All,

I would like to propose a new feature in the Cassandra row cache.

The proposition is for the use-case when you have a table where most of the read access is done on a few columns and the table has millions of rows.

To improve cache memory size I have 2 possible improvement propositions:


1)      Add options to row cache to select which columns should be cached

2)      Create the concept of VIEW (as most DBs have), where you could have different cache strategy approaches for the same Table

Let me know your thoughts.

[]'s
Felipe


[cid:image001.png@01D4E0B3.C8055EF0]
Felipe Perez
Cloud OTA Engineer
Gemalto is now part of the Thales Group.
Please note that my new email address is felipe.perez@thalesgroup.com<ma...@thalesgroup.com>
THALES
La Vigie, Avenue du Jujubier
ZI Athélia IV, 13705 La Ciotat Cedex, France
www.thalesgroup.com<http://www.thalesgroup.com>
[cid:image002.png@01D4E0B3.C8055EF0]<http://www.linkedin.com/company/thales> [cid:image003.png@01D4E0B3.C8055EF0] <https://twitter.com/thalesgroup>  [cid:image004.png@01D4E0B3.C8055EF0] <https://www.facebook.com/thalesgroup>  [cid:image005.png@01D4E0B3.C8055EF0] <https://www.youtube.com/user/thethalesgroup>

________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.