the WriteApi does not check whether a tag value cotains unauthorized characters ("\n","\r"...)

InfluxDB has some restrictions on tag values : they cannot contain some characters such as: line feed (\n), carriage return (\r). Currently, the Java client library does not check whether values of tags are safe (free of unauthorized characters) before writing them into InfluxDB.
For example, I have a measurement classe called Temperature, and it contains a tag field location. When I put location="mad\nrid" and I write it using WriteApi, it will throw the following exception: partial write: unable to parse 'temperature,location=mad': missing fields dropped=0. So a partial write will be done in the influxDB database: a new measurement rid will be mistakenly created, and it will contain only a part of the write.
If a tag value contains '\r', the java client will not even throw an exception, and it will perform an incorrect write into the database.

I think it would be really useful to add a method that ensures that tag values are correct before sending them to InfluxDB through the line protocol, in order to avoid incorrect writes and anomalous behaviors.

Commencez par suivre le chemin de WriteApi qui sérialise les valeurs des tags dans le line protocol d’InfluxDB. Vérifiez comment sont traitées les valeurs contenant un saut de ligne et un retour chariot, puis ajoutez une validation afin que les valeurs dangereuses ne puissent pas produire d’écritures partielles ou incorrectes ; utilisez les tests WriteApi existants, s’ils sont présents, pour couvrir les deux caractères.