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 e4532031e3
commit 7a7d44de51
1 changed files with 1 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -112,6 +112,7 @@ public class SensorDataAggregatorDaemon implements HalDaemon {
if(latestCompletePeriodEndTimestamp == maxTimestampFoundForSensor){ if(latestCompletePeriodEndTimestamp == maxTimestampFoundForSensor){
logger.fine("no new data to evaluate - aggregation is up to date"); logger.fine("no new data to evaluate - aggregation is up to date");
return;
}else{ }else{
logger.fine("evaluating period: "+ (maxTimestampFoundForSensor+1) + "=>" + latestCompletePeriodEndTimestamp + " (" + UTCTimeUtility.getDateString(maxTimestampFoundForSensor+1) + "=>" + UTCTimeUtility.getDateString(latestCompletePeriodEndTimestamp) + ") with expected sample count: " + expectedSampleCount); logger.fine("evaluating period: "+ (maxTimestampFoundForSensor+1) + "=>" + latestCompletePeriodEndTimestamp + " (" + UTCTimeUtility.getDateString(maxTimestampFoundForSensor+1) + "=>" + UTCTimeUtility.getDateString(latestCompletePeriodEndTimestamp) + ") with expected sample count: " + expectedSampleCount);
} }