/**   * Insert a new value keyed by key   * @param key Key for the value   * @param value the String value to insert   */  public void insert(final String key, final String value) throws Exception {    execute(new Command(){      public Void execute(final Keyspace ks) throws Exception {        ks.insert(key, createColumnPath(COLUMN_NAME), bytes(value));        return null;      }    });  }

  /**   * Get a string value.   * @return The string value; null if no value exists for the given key.   */  public String get(final String key) throws Exception {    return execute(new Command(){      public String execute(final Keyspace ks) throws Exception {        try {          return string(ks.getColumn(key, createColumnPath(COLUMN_NAME)).getValue());        } catch (NotFoundException e) {          return null;        }      }    });  }

  /**   * Delete a key from cassandra   */  public void delete(final String key) throws Exception {    execute(new Command(){      public Void execute(final Keyspace ks) throws Exception {        ks.remove(key, createColumnPath(COLUMN_NAME));        return null;      }    });  }

1. ^https://github.com/hector-client/hector/blob/master/README
2. ^https://github.com/hector-client/hector/releases
3. ^¹ {{cite web|url=http://prettyprint.me/2010/02/23/hector-a-java-cassandra-client/comment-page-1/|title=Hector – a Java Cassandra client|author=Ran Tavory|first=|date=|website=|publisher=PrettyPrint.me|location=http://prettyprint.me/|archive-url=|archive-date=|dead-url=|accessdate=2011-03-23|quote=Out of the box Cassanra provides a raw thrift client, which is OK, but lacks many features essential to real world clients. I’ve built Hector to fill this gap.
Here are the high level features of Hector, currently hosted at github.{{bulleted list|A high-level object oriented interface to cassandra.|Failover support.|Connection pooling.|JMX support.|Support for the Command design pattern to allow clients to concentrate on their business logic and let hector take care of the required plumbing.}}}}
4. ^{{cite web| accessdate = 2011-04-12| location = http://www.datastax.com/| publisher = DataStax| title = Hector Client for Apache Cassandra: Encapsulation of Thrift API| quote = Hector now completely encapsulates the Thrift API so developers have to deal only with the Hector client using familiar design patterns. The original API is still available for existing users to transition their current projects as well as for those who are comfortable working with Thrift.| url = http://www.datastax.com/sites/default/files/hector-v2-client-doc.pdf}}
5. ^{{cite web| accessdate = 2011-04-12| location = http://www.datastax.com/| publisher = DataStax| title = Hector Client for Apache Cassandra: Fully Mavenized| quote = Since the beta release of Cassandra 0.7.0, Riptano has been offering maven repository access for dependencies required for Cassandra usage via Hector.| url = http://www.datastax.com/sites/default/files/hector-v2-client-doc.pdf}}
6. ^{{cite web| accessdate = 2011-03-23| author = Ran Tavory| location = http://prettyprint.me/| publisher = PrettyPrint.me| title = Load balancing and improved failover in Hector.| quote = ve added a very simple load balancing feature, as well as improved failover behavior to Hector. Hector is a Java Cassandra client, to read more about it please see my previous post Hector – a Java Cassandra client. In version 0.5.0-6 I added poor-man’s load balancing as well as improved failover behavior.| url = http://prettyprint.me/2010/03/03/load-balancing-and-improved-failover-in-hector/}}
7. ^{{cite web| accessdate = 2011-04-12| location = http://www.datastax.com/| publisher = DataStax| title = Hector Client for Apache Cassandra: Availability of Metrics| quote = To facilitate smoother operations and better awareness of performance characteristics, Hector exposes both availability counters and, optionally, performance statistics through JMX.| url = http://www.datastax.com/sites/default/files/hector-v2-client-doc.pdf}}
8. ^{{cite web| accessdate = 2011-04-12| location = http://www.datastax.com/| publisher = DataStax| title = Hector Client for Apache Cassandra: Basic Load Balancing| quote = Hector provides for plugable load balancing through the LoadBalancingPolicy interface. Out of the box, two basic implementations are provided: LeastActiveBalancingPolicy (the default) and RoundRobinBalancingPolicy. LeastActiveBalancingPolicy routes requests to the pools with the lowest number of active connections. This ensures a good spread of utilization across the cluster by sending requests to the machine that has the least number of connections. RoundRobinBalancingPolicy implements a simple round-robin distribution algorithm.| url = http://www.datastax.com/sites/default/files/hector-v2-client-doc.pdf}}
9. ^{{cite web| accessdate = 2011-04-12| location = http://www.datastax.com/| publisher = DataStax| title = Hector Client for Apache Cassandra: Configuration of Pooling| quote = The behavior of the underlying pools of client connections can be controlled by the ExhaustedPolicy. […]| url = http://www.datastax.com/sites/default/files/hector-v2-client-doc.pdf}}