Influxdb doesn't allow duplicate data points

I think that influxdb should allow duplicate datapoints. So that for instance the following example should store a sequence of two field values (5,8) in a value field for a single timepoint:

datacollection value=5,value=8 1559260800000000000

I think it is common practice during data collection to have multiple data entries values for the same field at the same time point. Also, it is standard practice for processing systems to accept such a submission like on the web where it would be completely OK to GET or POST two seperate values to the same parameter name at the same URL in the same request.

I am aware of these workarounds (but do not think they are best practice!):
https://docs.influxdata.com/influxdb/v2.0/write-data/best-practices/duplicate-points/

...I have used these workarounds above for some time but I think that there is a bug in the design decision as it doesn't seem to follow neither application practice mentioned above when collecting data or neither the industry established practice from how other systems work.

The issue names no source files, tests, or entry points. Start by reviewing InfluxDB's duplicate-points guidance and the write path for how identical field keys and timestamps are handled. Done means the requested duplicate values have an explicit, tested storage and query behavior without relying on the listed workarounds.

Written by the indexing model from the issue text.