rantav/hector — Issue #406: Impossible to use MillisecondsClockResolution
Author: voitishchuk
Created: 2012-01-30 13:29:33+00:00
State: open

If ClockResolution set via CassandraHostConfigurator, hector still uses default MicrosecondsClockResolution.
ClockResolution set via CassandraHostConfigurator is never called.

Columns crated via hector have timestamp *1000 (in future) and connot be modified or deleted via cassandra-cli