056c8c3751
Fix typo in conf file
...
Just a small typo I noticed this morning
2014-03-16 13:58:28 +01:00
160bd6c9d4
Script to randomly write batches of points over a time interval.
2014-03-14 10:16:30 -04:00
d3124b3da5
Merge branch 'pr-318'
2014-03-13 16:37:05 -04:00
7bda031982
change the default log level to debug
2014-03-13 16:29:47 -04:00
df84b7fe79
fix few bugs introduced in dbe76df
...
The changes in that commit broke Join and Merge, because they were
bypassing the QueryEngine which kept track of the series that should be
closed at the end of the query. Aggregators require an empty time series
to be sent after the query ends to flush their internal state.
The other bug was in deletes. Fixing the first bug broke the new
behavior of deletes which is return nothing if the time series is
empty. This is also fixed.
2014-03-13 16:21:35 -04:00
f5706829e2
DRY the parser a little bit, we already have a definition for SELECT
2014-03-12 19:44:31 -04:00
f2e9c8a543
fix some log statements
2014-03-12 19:44:31 -04:00
e2adcf1c58
Close #318 . Support EXPLAIN queries
2014-03-12 19:44:31 -04:00
4da21ddc32
add some explain queries tests
2014-03-12 19:44:31 -04:00
dbe76dfa31
partial fix for issue #294 processing some queries in batches
2014-03-12 17:56:19 -04:00
e798c98bda
fix a broken test in the parser package
2014-03-12 17:14:50 -04:00
9fdf025f09
don't forget to include the version.go in the source tar file
2014-03-12 16:06:54 -04:00
36932ad604
remove the version from the influxd.go file
2014-03-12 16:00:01 -04:00
38b37bfcc7
update the changelog
2014-03-12 15:15:02 -04:00
4f30e59ea1
Merge pull request #333 from influxdb/fix-333-crypto-bug
...
"Failed to create user: crypto/blowfish: invalid key size 1"
2014-03-12 15:13:56 -04:00
0bc99d19fc
fix #333 . Readable error msgs and don't create user if pass is invalid
...
Currently we create a user with no password if the password provided was
not more than 4 chars and less than 56 chars. We also return an error
msg that reveals the internal of our crypto algorithm and isn't readable
by the end user.
2014-03-12 14:56:55 -04:00
fe2503f2dc
sleep for the data to replicate
2014-03-12 14:56:09 -04:00
87a284e131
remove redundant test
2014-03-12 14:52:58 -04:00
b4bdb45dd6
move the user manager interface to the api package
2014-03-12 14:52:58 -04:00
f9f00c63f1
set the process to nil after we kill the server
2014-03-12 14:10:30 -04:00
603621ee65
add some comments
2014-03-12 12:30:37 -04:00
b5f68b7c9d
update the changelog
2014-03-11 19:59:15 -04:00
b4babbd5d7
Merge pull request #302 from influxdb/fix-302-negative-time
...
Should be able to set negative times for dates before 1/1/1970
2014-03-11 19:09:04 -04:00
6b178a5b4f
Merge remote-tracking branch 'origin/fix-315-commits-not-in-order' into fix-302-negative-time
...
Conflicts:
src/cluster/shard.go
2014-03-11 19:04:42 -04:00
471039ac9b
fix #321 . Fix a off-by-one bug in the splitting algo
...
The algorithm that splits the data to multiple shards had an off-by-one
bug that caused one point from the next shard to be included in the
current shard.
2014-03-11 18:54:10 -04:00
7e659b92e3
make sure that a shard endtime is exclusive when we search for shards range
...
note: this is hard to test since the shards will only return points in
the given range, so even if we use more shards than we're supposed to
the returned points will not be outside the query range. The only way to
test this is to write a unit test.
2014-03-11 18:54:10 -04:00
3a5adb7e07
fix time stamp rounding when we create a new shard
2014-03-11 18:54:10 -04:00
94f06b76d2
add some logging
2014-03-11 18:54:10 -04:00
89e7eae8c6
fix the sleep since the process takes about 5 seconds to startup
2014-03-11 18:52:37 -04:00
3c664f4f08
fix #302 . Should be able to set negative times
2014-03-11 18:52:30 -04:00
a33bb3733d
fixup! we shouldn't be returning error if the function takes a response channel
2014-03-11 18:52:30 -04:00
64571fc972
Clean up test spacing.
2014-03-11 18:10:04 -04:00
c54588dd43
A massive group by test with real data.
2014-03-11 18:10:04 -04:00
fe10d5b1b0
Output the shard's start and end timestamps on String().
2014-03-11 18:10:04 -04:00
ef92908983
Add StartMicro and EndMicro methods to the shard.
2014-03-11 18:10:04 -04:00
e698a56552
sleep for a few seconds to give a chance for raft to replay the log
2014-03-11 16:32:52 -04:00
e1b996ea3a
more logging
2014-03-11 16:32:52 -04:00
5db312db88
fix a compilation error
2014-03-11 16:32:52 -04:00
5c56bfab91
change the name of the series in the test
2014-03-11 16:32:52 -04:00
2fe6fdc325
fix a bug, use value comparison instead of pointer comparison
2014-03-11 16:32:52 -04:00
ad99747e39
we shouldn't be returning error if the function takes a response channel
...
This is causing a bunch of deadlocks since those functions gets called
in a goroutine and their return values are never checked. Instead we
should return an endStreamResponse with the error message.
2014-03-11 16:32:52 -04:00
c33f94c14b
remove some logging statements
2014-03-11 16:32:52 -04:00
359584df3d
Drop the max delete size from 1M to 64K.
2014-03-11 14:31:50 -04:00
6fab943cbe
Revert "panic if we ever receive commits out of order"
...
This reverts commit 20a921eb32
2014-03-11 14:26:09 -04:00
bdb6cf43ff
fix a compilation error
2014-03-11 12:39:29 -04:00
4ede6f847e
fix #233 . Put back the code that limited the delete batch size
2014-03-11 12:38:55 -04:00
e0e7144c93
cleanup default start and end time code
2014-03-10 20:32:31 -04:00
710980c30e
fix a typo
2014-03-10 20:32:31 -04:00
b3c35ff2c6
Fix #315 . Make delete queries not use WAL. They should instead use Raft to replicate.
2014-03-10 18:10:02 -04:00
6dc127bde5
add a test to make sure invalid time group by interval don't crash the server
2014-03-10 17:33:35 -04:00
lucapette
Todd Persen
John Shahid
Pawel Szymanski
Paul Dix