influxdb-java drops data when using OneShotBatchWriter if any error is encountered

I understand that OneShotBatchWriter gets one shot to write its points to influxdb, but I found when importing historical data through influxdb-java, that the OneShotBatchWriter stops processing its list of BatchPoints as soon as an error happens.

Example:

  @Test
  public void test()
  {
    // Use OneShotBatchWriter
    db.enableBatch(5_000, 1, TimeUnit.SECONDS);

    // CPU might make it to influx, or might not depending on the order that OneShotBatchWriter writes them in
    db.write(databaseName,
             "one_day",
             Point.measurement("cpu")
                 .time(System.currentTimeMillis(), TimeUnit.MILLISECONDS)
                 .addField("cpu", 1)
                 .build());

    // Memory dropped by influxdb
    db.write(databaseName,
             "one_week",
             Point.measurement("memory")
                 .time(0, TimeUnit.MILLISECONDS)
                 .addField("memory", 1)
                 .build());

    db.disableBatch();
  }

The memory point is dropped by influxdb which results in an error back to influxdb-java, which promptly gives up on the cpu point. I like how simple OneShotBatchWriter is and don't need to retry points like RetryCapableBatchWriter, but could OneShotBatchWriter at least try all points?

Start at the OneShotBatchWriter entry point and reproduce the provided test scenario with the two BatchPoints, including one point that InfluxDB rejects. Trace how the error affects subsequent points and add coverage showing that all points are attempted; done means the valid CPU point is not dropped when the memory point fails.