Commit Graph

20 Commits (d16d11c47ee2350ba05b7136e425e52a52e551ec)

Author SHA1 Message Date
David Norton 08fb0c5997 Fix #780 so that fill works with all aggregates 2014-09-12 00:12:40 -04:00
John Shahid 655a092b5a Format the code 2014-09-08 15:50:29 -04:00
Nathaniel Cook c8c40097c6 Making histogram alignment easier to control
Fix #669
2014-09-08 15:37:20 -04:00
John Shahid 71ccbdc99c Don't panic on invalid boolean operators
Close #714
2014-09-08 14:35:31 -04:00
John Shahid e1bb3be735 Fix case insensitive regex matching
Close #794
2014-09-08 14:04:12 -04:00
John Shahid 3c9b39ce01 Return an error if an invalid column is used to filter after a join
Fix #652
2014-09-04 12:35:07 -04:00
John Shahid fa6208ad33 Remove unused methods 2014-09-03 15:10:43 -04:00
John Shahid 2c55e04188 Move things around 2014-09-03 15:10:43 -04:00
John Shahid 0a0b14ba23 Remove more constants 2014-09-03 15:10:43 -04:00
John Shahid 4d666fc3dc rename 2014-09-03 15:10:43 -04:00
John Shahid 1606fdad95 Add a comment 2014-09-03 15:10:43 -04:00
John Shahid 8df689dbd5 Refactor bucket traversing in its own struct 2014-09-03 15:10:43 -04:00
John Shahid 93e75e4c13 Add some logging 2014-09-03 15:10:43 -04:00
John Shahid 4383375fe8 Split the different engines in their own types 2014-09-03 15:10:43 -04:00
John Shahid 59ab59dd2a Remove an unused interface 2014-09-03 15:10:43 -04:00
John Shahid 680e6d96bc Always fill empty groups if the start time is specified.
Prior to this change, empty group filling worked between t1 and t2,
where t1 is the timestamp of the earliest point and t2 is the timestamp
of the last point. This patch change the behavior of the fill() to use
the query start and end time as t1 and t2, respectively. This only
happens if the user specified the start time of the query. Otherwise,
there's a potential of filling millions of millions of groups, since the
default start time of the query is really really early.
2014-08-06 16:03:29 -04:00
John Shahid 031f4adf47 Remove an unused statement 2014-08-04 12:53:00 -04:00
John Shahid 72fccdab6f Don't emit non existent fields when joining
Points in the joined series should have either the columns of the left
side or the columns of the right side of the join. Before this patch
join relied on merge to order the points of the two series and then join
consecutive points together. The merge emitted the union of the columns
of the two series, which caused the joined series to always have the
union of two series. This combined with the fact that the point's values
weren't adjusted to have nulls for the missing columns caused panic when
any operation is done on the points, e.g. addition.

Fix #740, Fix #781
2014-07-30 14:06:47 -04:00
Philip O'Toole c1e285383b Allow 'null' to be supplied as fill value
Add to unit tests to test fill, including new "null" support.

Fix #713.
2014-07-22 15:07:11 -04:00
John Shahid e5276112c1 Restructure the codebase to be more idiomatic 2014-06-30 11:31:08 -04:00