i have the same trouble concerning “where-condition-propagation”. I used the same query structure as mentioned above! In recent feature discussions this behaviour is described by the influx developers.
AFAIK today it is not possible to return points in time which are NOT within a specific time range!!!
An clause like “WHERE NOT IN” would be very nice…
My case is to determine the age of the latest point in time relative to now(), and then check if the user has not been active within the last n minutes.
The “elapsed()” function does not return the timespan with respect to the left/right interval boundary -> THIS woulld be a nice FEATURE!!! -> then the elapsed time concerning the first point would be calculated with respect to now()…
Why should a TSDB not have such an (important) time related functionality?