influxdata/influxdb-scala

Scala client for InfluxDB

The v1 client libraries for InfluxDB were typically developed and maintained by community members. They have all now been succeeded by v2 client libraries. They are being archived it in favor of the v2 client library. See #7.

If there are still users of this v1 client library, and they or somebody else are willing to keep them updated with security fixes at a minimum please reach out on the Community Forums or InfluxData Slack.

influxdb-scala

Latest Scala client can be found here: https://github.com/influxdata/influxdb-client-java/tree/master/client-scala

This library is not updated for InfluxDB 0.9. There are breaking changes to the API, use at your own risk.

We encourage you to submit a pull request if you have a contribution. If you make a PR please explicitly call @beckettsean to get eyes on your PR.

---

Scala client for InfluxDB heavily inspired by influxdb-go.

influxdb-scala's Issues

Activity?

Is this still maintained? Can it be downloaded via sbt? Why do the APIs not use Futures?

Identify repo owner and move to InfluxCommunity org

The v1 client libraries for InfluxDB were typically developed and maintained by community members. They have all now been succeeded by v2 client libraries developed and maintained by InfluxData in partnership with Bonitoo.

If there are still users of this v1 client library, and they or somebody else are willing to keep them updated with security fixes at a minimum, this code should be moved to https://github.com/InfluxCommunity and control of it given to the new maintainers. Otherwise let's archive it in favor of the v2 client library.

Please Update for Influx 1.x and 2.x

Have had several requests for an updated Scala client for Influx 1.x and 2.x. This will also make it easier to connect to Spark.

API Cleanup: A couple ideas

Hey guys,

I'm liking InfluxDB so far but the API for this makes me slightly sad.

• Can we have everything accept Seq[...] instead of Array[...]? Seqs are much more flexible and easier to work with.
• It's not considered good Scala style to have var's especially in the Client class constructor. You don't really want to allow someone to change the database name in the middle of using the client.
• I think a much better API than Array[Array[Any]] would be to have WriteSeries take case classes. Scala macros can deduce the fields from the case classes, and this way it is type safe. Using a Array[Any] forces boxing of all numeric values, which is very slow and expensive, and it is not type safe at all.

I might be interested in submitting PRs but wanted to run these things by you guys first.

Also, how about packaging and submitting jars to Maven Central, or at least Bintray (much easier than Maven Central)?

Make this available in maven central

If you want people to use this you should release to maven central.

More info on releasing through sonatype oss with sbt
http://www.cakesolutions.net/teamblogs/publishing-artefacts-to-oss-sonatype-nexus-using-sbt-and-travis-ci