Fix example server_data to support v0.9 #115
Conversation
This includes fixes for the private method '_query' from client.py to work properly with influxdb v0.9 API
|
|
|
Keep in mind that you can no longer query with a specific precision:
|
|
I like the idea of not having to set database all the time, maybe we should open a new ticket to follow up on this. |
|
See last commit, it removes the query method and make query method compliant with dataframe_client |
| @@ -276,6 +297,7 @@ def _write_points(self, | |||
| if self.use_udp: | |||
| self.send_packet(data) | |||
| else: | |||
| import ipdb; ipdb.set_trace() | |||
|
I often have the bad habbits to count on travis-ci to run the tests :) |
| @@ -195,21 +195,40 @@ def query(self, | |||
| query, | |||
| params={}, | |||
| expected_response_code=200, | |||
| time_precision='s', | |||
There was a problem hiding this comment.
There is no time precision in queries.
see: http://influxdb.com/docs/v0.9/concepts/reading_and_writing_data.html
The format of the returned timestamps complies with RFC3339, and has nanosecond precision
|
I'll take care of it. |
|
Ok I'm leaving this to you |
|
@areski Thanks =) |
This includes fixes for the private method '_query' from client.py to work
properly with influxdb v0.9 API