BatchWriter flushing?

[ryantheleach]

I would like to see a method to flush the batch writer immediately and await until it's flushed.

Knowing the data is flushed to Influx can be important when copying data between 2 different retention policies.

We are trying to implement a 'quarantine' feature, where we can highlight data ranges that need to be kept indefinitely.

[AlecsandruDuma]

I need this too. Either I do not understand how batchWriter should be used, or nobody until now cared if points sent to the writer were actually written into InfluxDB. When I close my application last several points are not written. Please advise. Thanks.

[ryantheleach]

@AlecsandruDuma I ended up making my own batch writer, unfortunately it's not open source and I can't make it open source. However, it was fairly trivial.

[tihomir-kit]

I simply didn't need it so far, so I didn't implement that initially as a part of the BatchWriter. If you need it asap, I'll welcome a PR. But I won't be able to push a new release of the lib in the next 1-2 months because I'm busy with some other things. If you can wait, I'll add it for the next release myself.

Currently the batch writer simply flushes every XY milliseconds and doesn't handle any tails. You can either ensure in your app that you "wait" for that amount of MS before actually killing your app, or add a .StopAndFlush() to the library and I'll merge it in when I have the time.

And the BatchWriter will probably require implementation of IDisposable so the .StopAndFlush() gets called automatically.