Matches in DBpedia 2016-04 for { <http://blog.octo.com/en/nosql-lets-play-with-cassandra-part-13/> ?p ?o }
Showing triples 1 to 14 of
14
with 100 triples per page.
- nosql-lets-play-with-cassandra-part-13 accessdate "2011-03-23".
- nosql-lets-play-with-cassandra-part-13 author "Olivier Mallassi".
- nosql-lets-play-with-cassandra-part-13 date "2010-06-09".
- nosql-lets-play-with-cassandra-part-13 isCitedBy Atomicity_(database_systems).
- nosql-lets-play-with-cassandra-part-13 isCitedBy Elasticity_(data_store).
- nosql-lets-play-with-cassandra-part-13 isCitedBy Eventual_consistency.
- nosql-lets-play-with-cassandra-part-13 location en.
- nosql-lets-play-with-cassandra-part-13 publisher "OCTO Talk!".
- nosql-lets-play-with-cassandra-part-13 publisher "OCTO Talks!".
- nosql-lets-play-with-cassandra-part-13 quote "Atomicity is also weaker than what we are used to in the relational world. Cassandra guarantees atomicity within a so for all the columns of a row.".
- nosql-lets-play-with-cassandra-part-13 quote "Elasticity “Cassandra is liquid” would have written any marketer and [...] a lot of NoSQL solutions have been built upon this DNA. First of all, elasticity is at the data modeling level. Your data will live longer than your business rules and softness in the way your data schemas can evolve across the time is an interesting point. But elasticity is also about infrastructure and cluster sizing. Adding a new node to Cassandra is simple. Just turn on the AutoBootstrap property and specify at least one Seed of the current cluster. The node will hence be detected, added to the cluster and the data will be relocated . Decommissioning a node is almost as simple as adding a node except you need to use the nodetool utility or a JMX command.".
- nosql-lets-play-with-cassandra-part-13 quote "Of course, at a given time, chances are high that each node has its own version of the data. Conflict resolution is made during the read requests and the current version of Cassandra does not provide a Vector Clock conflict resolution mechanisms [sic] . Conflict resolution is so based on timestamp : the higher timestamp win[s] and the node you are reading the data [from] is responsible for that. This is an important point because the timestamp is specified by the client, at the moment the column is inserted. Thus, all Cassandra clients’ [sic] need to be synchronized...".
- nosql-lets-play-with-cassandra-part-13 title "Let’s play with Cassandra…".
- nosql-lets-play-with-cassandra-part-13 url nosql-lets-play-with-cassandra-part-13.