group-by on time returns data out of order about influxdb HOT 3 CLOSED

Fixed. Please give it another try and reopen if the issue is still reproducible with the latest version.

from influxdb.

seems to work perfectly.

I was surprised you had to do a sort... but looks like you are doing a mini-map-reduce on the parts. interesting!

thanks,

1384394690000 10000 99
1384394680000 10000 99.1
1384394670000 10000 99
1384394660000 10000 98.9
1384394650000 10000 99.1
1384394640000 10000 99.1
1384394630000 10000 99.1
1384394620000 10000 99
1384394610000 10000 99
1384394600000 10000 99.1
1384394590000 10000 99.2
1384394580000 10000 99.1
1384394570000 10000 99.1
1384394560000 10000 99
1384394550000 10000 99.1
1384394540000 10000 99.1

from influxdb.

There are definitely some optimizations that can be applied here. I'm
inclined not to prematurely optimize given that the code base is still
young and changes very rapidly. Once the code base is mature enough we'll
run benchmarks and take care of the bottlenecks and inefficient code paths.
On Nov 13, 2013 9:06 PM, "Nick Galbreath" [email protected] wrote:

seems to work perfectly.

I was surprised you had to do a sort... but looks like you are doing a
mini-map-reduce on the parts. interesting!

thanks,

1384394690000 10000 99
1384394680000 10000 99.1
1384394670000 10000 99
1384394660000 10000 98.9
1384394650000 10000 99.1
1384394640000 10000 99.1
1384394630000 10000 99.1
1384394620000 10000 99
1384394610000 10000 99
1384394600000 10000 99.1
1384394590000 10000 99.2
1384394580000 10000 99.1
1384394570000 10000 99.1
1384394560000 10000 99
1384394550000 10000 99.1
1384394540000 10000 99.1

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-28453801
.

from influxdb.