this will work.I have tried both gave one day unique bucket.
I just realized, If I sync all clients to one zone then date will remain
same for all.
One Zone date will give materialize view to row.
On Mon, Apr 30, 2012 at 11:43 PM, samal wrote:
> hhmm. I will try both. thanks
>
>
> On Mon, Apr
hhmm. I will try both. thanks
On Mon, Apr 30, 2012 at 11:29 PM, Tyler Hobbs wrote:
> Err, sorry, I should have said ts - (ts % 86400). Integer division does
> something similar.
>
>
> On Mon, Apr 30, 2012 at 12:39 PM, samal wrote:
>
>> thanks I didn't noticed.
>> run script for 5 minutes => d
Err, sorry, I should have said ts - (ts % 86400). Integer division does
something similar.
On Mon, Apr 30, 2012 at 12:39 PM, samal wrote:
> thanks I didn't noticed.
> run script for 5 minutes => divide seems to produce result ,modulo is
> still changing. If divide is ok will do the trick.
> I
thanks I didn't noticed.
run script for 5 minutes => divide seems to produce result ,modulo is
still changing. If divide is ok will do the trick.
I will run this script on Singapore, East coast server, and New delhi
server whole night today.
==
unix => 133580698
getTime() returns the number of milliseconds since the epoch, not the
number of seconds: http://www.w3schools.com/jsref/jsref_gettime.asp
If you divide that number by 1000, it should work.
On Mon, Apr 30, 2012 at 11:28 AM, samal wrote:
> I did it with node.js but it is changing after some inter
I did it with node.js but it is changing after some interval.
setInterval(function(){
var d =new Date().getTime();
console.log("== ");
console.log("unix => ",d);
i=parseInt(d)
console.log("Divid i/86400=> ",i/86400);
console.log("Modulo i%86400=> ",i%8640
Correct, that's exactly what I'm saying.
On Mon, Apr 30, 2012 at 10:37 AM, samal wrote:
> thanks tyler for reply.
>
> are you saying user1uuid_*{ts%86400}* would lead to unique day bucket
> which will be timezone {NZ to US} independent? I will try.
>
>
> On Mon, Apr 30, 2012 at 8:25 PM, Tyler H
thanks tyler for reply.
are you saying user1uuid_*{ts%86400}* would lead to unique day bucket
which will be timezone {NZ to US} independent? I will try.
On Mon, Apr 30, 2012 at 8:25 PM, Tyler Hobbs wrote:
> Don't use dates or datestamps as the buckets for your row keys, use a unix
> timestamp
Don't use dates or datestamps as the buckets for your row keys, use a unix
timestamp modulo whatever size you want your bucket to be instead.
Timestamps don't involve time zones or any of that nonsense.
So, instead of having keys like "user1uuid_30042012", the second half would
be replaced the cur
Hello List,
I need suggestion/ recommendation on time series data.
I have requirement where users belongs to different timezone and they can
subscribe to global group.
When users at specific timezone send update to group it is available to
every user in different timezone.
I am using GroupSubscr
10 matches
Mail list logo
