a79d6104d5
Documentation fixups
2013-08-01 16:24:51 -04:00
8e8ec59e30
Support "nilmtool cmd --version"
2013-08-01 15:14:34 -04:00
b89b945a0f
Better responses to invalid HTTP times
2013-07-31 13:37:04 -04:00
bd7bdb2eb8
Add --optimize option to nilmtool intervals
2013-07-30 15:31:51 -04:00
840cd2fd13
Remove stray print
2013-07-30 15:21:09 -04:00
bbd59c8b50
Add nilmdb.utils.interval.intersection by generalizing set_difference
2013-07-30 14:48:19 -04:00
6cd28b67b1
Support iterator protocol in Serializer
2013-07-24 14:52:26 -04:00
d6d215d53d
Improve boolean HTTP parameter handling
2013-07-15 14:38:28 -04:00
e02143ddb2
Remove duplicated test
2013-07-14 15:30:53 -04:00
fc43107307
Fill out test coverage
2013-07-09 19:06:26 -04:00
b5df575c79
Fix tests
2013-05-09 22:27:10 -04:00
9a2699adfc
Attempt at fixing up more Unicode issues with metadata.
2013-05-07 13:44:03 -04:00
539c92226c
Add more disk space info
2013-05-06 11:36:28 -04:00
49d04db1d6
Allow start==end in stream_insert_context, if no data was provided.
2013-04-11 13:25:37 -04:00
ea838d05ae
Warn against reused context managers, and fix broken tests
2013-04-11 13:25:00 -04:00
f2a48bdb2a
Test binary extract; fix bugs
2013-04-11 13:24:11 -04:00
b98ff1331a
Fix bug where too much data was getting written to each file.
...
We were still calculating the maximum number of rows correctly,
so the extra data was really extra and would get re-written to the
beginning of the subsequent file.
The only case in which this would lead to database issues is if the
very last file was lengthened incorrectly, and the "nrows" calculation
would therefore be wrong when the database was reopened. Still, even
in that case, it should just leave a small gap in the data, not cause
any errors.
2013-04-10 23:22:03 -04:00
01029230c9
Tweaks to sorting
2013-04-10 19:59:38 -04:00
ecc4e5ef9d
Improve test coverage
2013-04-10 19:08:05 -04:00
416a499866
Support wildcards for destroy
2013-04-10 16:23:07 -04:00
0104c8edd9
nilmtool remove: allow wildcards and multiple paths
2013-04-10 15:27:46 -04:00
cf3b8e787d
Add test for wrong number of fields in numpy insert
2013-04-10 15:06:50 -04:00
83d022016c
nilmtool list: add new --layout option to show layouts
2013-04-10 14:58:44 -04:00
43b740ecaa
nilmtool list: remove old -p parameter
2013-04-10 14:48:23 -04:00
230ec72609
Fix timestamp display issues with --annotate
2013-04-09 18:19:32 -04:00
e95142eabf
Huge update to support inserting in client.numpyclient, with tests
...
This includes both client.stream_insert_numpy and
client.stream_insert_numpy_context(). The test code is based on
similar test code for client.stream_insert_context, so it should be
fairly complete.
2013-04-08 18:51:45 -04:00
d21c3470bc
Client cleanups; fix tests to account for time epsilon = 1
2013-04-08 18:51:45 -04:00
cc211542f8
Add binary support to nilmdb.server; enforce content-type
2013-04-08 18:51:45 -04:00
8292dcf70b
Clean up stream/extract content-type and add a test for it
2013-04-08 18:51:45 -04:00
41ec13ee17
Rename bulkdata.append_string to bulkdata.append_data
2013-04-08 18:51:45 -04:00
c7f2df4abc
Add nilmdb.client.numpyclient.NumpyClient with stream_extract_numpy
...
This is a subclass of nilmdb.client.client.Client that adds numpy
specific routines, which should be a lot faster.
2013-04-07 17:43:52 -04:00
5b7409f802
Add binary extract to client, server, nilmdb, bulkdata, and rocket.
2013-04-07 16:06:52 -04:00
9ce0f69dff
Add "--delete" option to "nilmtool metadata" tool
...
This is the same as "--update" with an empty string as the value.
2013-04-02 16:07:28 -04:00
ebccfb3531
Fix stream renaming when the new path is a parent of the old
2013-04-01 19:25:17 -04:00
173121ca87
Switch URL to one that should definitely not resolve
2013-03-30 17:31:35 -04:00
26bab031bd
Add StreamInserter.send() to trigger intermediate block send
2013-03-30 17:30:43 -04:00
f8ca8d31e6
Remove Iteratorizer, as it's no longer needed
2013-03-24 21:31:03 -04:00
ed89d803f0
Remove aplotter code
2013-03-24 21:29:09 -04:00
3d24092cd2
Replace bare 'except:' with 'except: Exception'
...
Otherwise we might inadvertently catch SystemExit or KeyboardExit or
something we don't want to catch.
2013-03-24 21:28:01 -04:00
c0d450d39e
Add locking mechanism to avoid multiple servers on one DB
2013-03-24 21:20:20 -04:00
e790bb9e8a
Fix test failure when tests are run as root
2013-03-21 14:33:02 -04:00
89be6f5931
Add option to include interval start/end markup on extract
...
When enabled, lines like "# interval-start 1234567890123456" and "#
interval-end 1234567890123456" will be added to the data output. Note
that there may be an "interval-end" timestamp followed by an identical
"interval-start" timestamp, if the response at the nilmdb level was
split up into multiple chunks.
In general, assume contiguous data if previous_interval_end ==
new_interval_start.
2013-03-19 14:23:33 -04:00
4cdef3285d
Destroy now requires that all data has been previously removed.
...
Added new flag "-R" to command line to perform an automatic removal.
This should be the last of the ways in which a single command could
block the nilmdb thread for a long time.
2013-03-18 19:39:03 -04:00
bcd82c4d59
Limit the number of rows removed per call to nilmdb.stream_remove
...
Server class will retry as needed, as with stream_extract and
stream_intervals.
2013-03-18 18:22:45 -04:00
2d72891162
Accept "min" and "max" as timestamps on command line
2013-03-18 18:19:24 -04:00
0ef71c193b
Remove layout.pyx, since rocket replaced it
2013-03-15 22:32:40 -04:00
22274550ab
Test python version of Interval too
2013-03-15 21:37:03 -04:00
4f06d6ae68
Move Interval set_difference inside nilmdb.utils for clients
...
Clients might need to to Interval math too, so move a simple Interval
class and start putting helpers in there.
2013-03-15 21:37:03 -04:00
c54d8041c3
Update design docs
2013-03-15 21:07:01 -04:00
049375d30e
Fill out test coverage
2013-03-15 18:08:21 -04:00
