Currently, there is no difference between float and integer data types when exporting fields values via InfluxDB line protocol. It means, for example, that float 5 and integer 5 will look the same:

myMeasurement floatField=5,integerField=5

As a result, in InfluxDB they both will be treated as floats so won't be as efficient as possible.

InfluxDB documentation says that integer field values should have the i suffix to be treated as integers eventually:

Signed 64-bit integers.
Trailing i on the number specifies an integer.

See for details: Integer

So I propose to fix integer data type exporting and use the i suffix in the Line protocol.

The example above with this change will look like this:

myMeasurement floatField=5,integerField=5i