I've updated the DataModel page on the wiki to reflect this discussion.
http://wiki.apache.org/cassandra/DataModel
~Noah
On Sun, Mar 21, 2010 at 9:46 PM, Michael Pearson wrote:
> Just a note for PHP users that using microtimes with the
> thrift_protocol module won't work on 32-bit machines
> (ht
Just a note for PHP users that using microtimes with the
thrift_protocol module won't work on 32-bit machines
(https://issues.apache.org/jira/browse/THRIFT-729).
.michael.
On Sun, Mar 21, 2010 at 8:51 AM, Jonathan Ellis wrote:
> Looks like consensus is that "microseconds since epoch" is the way
Looks like consensus is that "microseconds since epoch" is the way to
go. I've updated the cli to do this. (Will be in the release after
0.6 beta3.)
-Jonathan
On Thu, Mar 18, 2010 at 3:37 PM, Jeff Hodges wrote:
> As one of the committers to cassandra.gem, microseconds is the way to
> go. Speci
On Thu, Mar 18, 2010 at 3:20 PM, Michael Malone wrote:
> A standard default would be nice, but while we're making recommendations
> I'd also suggest that client libs should make this parameter easy to
> override. Client apps can do lots of interesting things by setting
> timestamps explicitly. Yo
On Thu, 18 Mar 2010 13:20:34 -0700 Michael Malone wrote:
MM> A standard default would be nice, but while we're making
MM> recommendations I'd also suggest that client libs should make this
MM> parameter easy to override. Client apps can do lots of interesting
MM> things by setting timestamps exp
As one of the committers to cassandra.gem, microseconds is the way to
go. Specificity is nice to have when you haven't been thinking about
timestamps and suddenly have a deep, abiding need to care about them.
I cannot understate that. It is much easier to remove the specificity
than it is to put i
A standard default would be nice, but while we're making
recommendations I'd also suggest that client libs should make this
parameter easy to override. Client apps can do lots of interesting
things by setting timestamps explicitly. You can get a sort of quasi-
transaction by using the same t
+1 I think this is a great idea. I've been bitten by this when switching
clients, and it took a while to figure out what was going on. Good job on
pycassa, vomjom!
-Ben
2010/3/18 Ted Zlatanov
> On Thu, 18 Mar 2010 02:36:35 -0500 Jonathan Hseu
> wrote:
>
> JH> Jonathan Ellis suggested that I
On Thu, 18 Mar 2010 02:36:35 -0500 Jonathan Hseu wrote:
JH> Jonathan Ellis suggested that I bring this issue to the dev mailing list:
JH> Cassandra should recommended a default timestamp across all clients
JH> libraries.
...
JH> Here's what different clients are using:
JH> 1. Cassandra CLI: Mil
Jonathan Ellis suggested that I bring this issue to the dev mailing list:
Cassandra should recommended a default timestamp across all clients
libraries.
Many users on IRC are having difficulty when using different clients because
different clients are using different timestamps. If you insert wi
10 matches
Mail list logo
