ziver/hal
1
1
Fork 0
Code Pull requests Releases Activity

Resolved a trace where a timestamp had an faulty offset of -1 in the aggregation deamon

Browse source
This commit is contained in:
Daniel Collin 2016-02-19 10:08:33 +01:00
parent 5f5597dae4
commit e4532031e3
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/se/hal/deamon/SensorDataAggregatorDaemon.java
View file

@ -110,7 +110,7 @@ public class SensorDataAggregatorDaemon implements HalDaemon {
long latestCompletePeriodEndTimestamp = new UTCTimePeriod(aggregationStartTime, aggrPeriodLength).getPreviosPeriod().getEndTimestamp();
long oldestPeriodStartTimestamp = new UTCTimePeriod(aggregationStartTime-ageLimitInMs, aggrPeriodLength).getStartTimestamp();
if(latestCompletePeriodEndTimestamp == oldestPeriodStartTimestamp){
if(latestCompletePeriodEndTimestamp == maxTimestampFoundForSensor){
logger.fine("no new data to evaluate - aggregation is up to date");
}else{
logger.fine("evaluating period: "+ (maxTimestampFoundForSensor+1) + "=>" + latestCompletePeriodEndTimestamp + " (" + UTCTimeUtility.getDateString(maxTimestampFoundForSensor+1) + "=>" + UTCTimeUtility.getDateString(latestCompletePeriodEndTimestamp) + ") with expected sample count: " + expectedSampleCount);