Comparison between integer and float should work

[affo]

A pushed down filter transformation in Flux returned no values because it was comparing double with an integer.

That comparison should work.

Line protocol data:

temperature,sensor=S1 value=30 1567512280951
smoke,sensor=S1 value=false 1567512280951
temperature,sensor=S1 value=40 1567512340951
smoke,sensor=S1 value=true 1567512340951
temperature,sensor=S1 value=55 1567512400951
smoke,sensor=S1 value=true 1567512400951
temperature,sensor=S1 value=55 1567512460951
smoke,sensor=S1 value=true 1567512460951
temperature,sensor=S1 value=55 1567512520951
smoke,sensor=S1 value=true 1567512520951

No data from this query:

from(bucket: "training")
  |> range(start: 2019-09-03T12:00:00Z, stop: 2019-09-03T12:10:00Z)
  |> filter(fn: (r) => r._measurement == "temperature")
  |> filter(fn: (r) => r.sensor == "S1")
  |> filter(fn: (r) => r._value > 50)

Data from this one:

from(bucket: "training")
  |> range(start: 2019-09-03T12:00:00Z, stop: 2019-09-03T12:10:00Z)
  |> filter(fn: (r) => r._measurement == "temperature")
  |> filter(fn: (r) => r._field == "value")
  |> filter(fn: (r) => r.sensor == "S1")
  |> filter(fn: (r) => r._value > float(v:50))

This should be a bug in InfluxDB, because that filter is pushed down to storage by Flux.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[affo]

I think this is still relevant

[russorat]

this should be solved when this epic is closed. please follow it for updates. influxdata/flux#3348