If multiple databases were specified, then the earlier writes would be
written to the later database and/or retention policy because points
were only written out after the batch size was reached. This forces the
batcher to flush whenever the database context switches.
This reverts commit 9aeae7ce82, reversing
changes made to 35b44cc2f0.
The contributor was unable to sign the contributor license agreement so
we have to revert this commit.
batchWrite was using the last database and retention policy read from
the input file. Because batchWrite was called only every batchSize lines
or at EOF, databases with fewer than batchWrite points could be imported
into the incorrect database.
This change forces a flush with batchWrite whenever processDML reads a
change in database or retention policy.
We no longer insert the `upgrade_artifiact`. Instead we now just use the entire series name as the measurement name.
Add info on throttling as well as status messages.