TODO

[aviau]

TODO LIST

• Review the docs
• Update and test all the tutorials
• Fix the DataFrameClient and improve coverage (see DataFrameClient with 0.9.0 #108 )
• Implement more operations (user management, etc.)

DONE

• Debug UDP support (I couldn't get it working)
• Fix the SeriesHelper
• Support writing in batch (see batch_size logic in write_points too soon leaves the loop #102)

[dashesy]

I have a small working library that plan to make it into Pandas, you can take a look if you want here

[aviau]

@dashesy Would you keep me updated on that please? If this is ever merged in pandas I would love to support it in the lib.

[areski]

The test coverage on DataFrameClient is quite weak, it might be nice to add this to the TODO.

[aviau]

Noted.

[cannium]

As I noticed, InfluxDB v0.9 supports clustering. Does influxdb-python supports connecting to multiple hosts(a cluster) now? I think the new version should handle clustering properly.

[gst]

about :

Debug UDP support (I couldn't get it working)

it's (very "simply", with write_points() method) tested in last version.. within class UdpTests.. which could probably be extended with others udp tests more advanced, eventually.

[cannium]

I posted a pull request for clustering. Please review.

[gst]

@ReAzem
I was still asking myself why you tagged "so quickly" and more important : why you taggeg with v1.0.0.. (and then after 1.0.1 & 1.0.2)..

we could have had/followed the same (at least major) version than the server.. now it's over unless we delete the tags.. (which I'd vote for but it depends..)

wdyt ?

[aviau]

@gst

The versioning of the lib has nothing to do with the versioning of the server. This is not the same project.

I am following the Semantic Versioning spec.

major.minor.patch

Everytime the API breaks: major release
Every new feature: minor release
Every bug patch/fix: patch release

The next tag will be 2.0.0 because we broke the API with ResultSet.

[gst]

The versioning of the lib has nothing to do with the versioning of the server. This is not the same project.

that is a shame ! ;) no kidding ;) Ofcourse there aren't the same project :p but they are quite tightly coupled.. aren't they ?
I find that it's quite often that a client follow the same version (at least major) than the server for which it is the client .. just for the sake of clarity / simplicity..
examples : mysql , postgres , others..

then why did you raised from v0.4.1 to v1.0.0 .. ? we certainly could have had v0.9-rcXX :s

The next tag will be 2.0.0 because we broke the API with ResultSet.

because you already tagged v1.0.0 previously ;) which I still don't see a/the reason actually..

[aviau]

I find that it's quite often that a client follow the same version (at least major) than the server for which it is the client

Can't do that and respect semver at the same time. I think semver is more important than this.

then why did you raised from v0.4.1 to v1.0.0 .. ? we certainly could have had v0.9-rcXX :s

I wanted to release to PyPI ASAP because of the influxdb08 sub-module. This was a good time so I released 1.0.0. 1.0.0 should have been released a long time ago, I didn't manage versioning at this time.

See the Semver Specification:

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

[gst]

ok for the Semver spec..

but hell :

How do I know when to release 1.0.0?
If your software is being used in production, it should probably already be 1.0.0.

:| there are people using influxdb-server (but v0.8 then...) and its python-client in production (which should then be influxdb-python v0.4.1 ....) ??

[aviau]

:| there are people using influxdb-server (but v0.8 then...) and its python-client in production (which should then be influxdb-python v0.4.1 ....) ??

Yes. See here (hopefully it all worked out for him!):

/pull/99
ChristopherRabotin:
I hope to start using influxdb in prod starting the middle of next week. :D

InfluxDB 0.5.0 was announced as ready for production: http://influxdb.com/blog/2014/03/24/influxdb_v0_5_0_ready_for_production.html

I will absolutely keep respecting the semver spec. I will also never revert a tag. PyPI won't let me do it and its just terrible practice anyways.