Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fill(previous) does not really get previous value #2496

Closed
paaland opened this issue May 6, 2015 · 2 comments
Closed

fill(previous) does not really get previous value #2496

paaland opened this issue May 6, 2015 · 2 comments

Comments

@paaland
Copy link

paaland commented May 6, 2015

fill(previous) works only on the current time span (the where statement). I expected it to use the previously logged value at or before the current time span.

Say I have the value 100 logged at 2014-12-31
And the value 50 logged at 2015-01-02

The I perform the query:

select value from someSeries where time > '2015-01-01' group by time(24h) fill(previous)

It returns
2015-01-01 null
2015-01-02 50
2015-01-03 50
2015-01-04 50
and so on

I would expect it to return 100 as the value for 2015-01-01 when specifying fill(previous) even though the value 100 was logged outside of the time scope.

In other historian db's you have the notion of "include bounds" which will include the last value before as well as the first value after your specified time range. These can be used to fill in manually.

Very useful when working with devices that only logs new data points on actual change. It can be quite large gaps without any data logged. When viewing the data I don't want "holes" in the series.

@beckettsean beckettsean added this to the Next Point Release milestone May 6, 2015
@beckettsean beckettsean added area/queries status/help-wanted difficulty/medium Resolving this issue should take up to a week labels May 6, 2015
@beckettsean
Copy link
Contributor

Ported from comment on #1925. Thanks, @paaland!,

@beckettsean beckettsean added RFC and removed difficulty/medium Resolving this issue should take up to a week status/help-wanted labels May 7, 2015
@beckettsean beckettsean modified the milestones: Next Point Release, Longer term Aug 6, 2015
@jsternberg
Copy link
Contributor

Closing this in favor of the more recent #5943.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants