GitLab

- When the start and end timestamps of a query are equal, it is enforced
that only one sensor value will be retrieved

- Staleness checks when performing sensor queries in the cache are
now enforced both in relative and absolute modes
- Fixed a race condition causing wrong results when performing queries
in absolute mode
- Changed logging in the TesterAnalyzer plugin

- Fixed a fair amount of bugs related to job analyzers
- Added a "getJobsInIntervalRunning" method to JobDataStore, to get
the list of jobs that were running in a certain time interval
- Some code refactoring for the JobDataStore class to reduce duplication
- Job analyzers have been tested and are working properly as of now

- Now supports also standard deviation and percentile computation
- Multiple output sensors per analyzer can be defined, each performing
a different aggregation task
- QueryEngine has been slightly modified so as not to clear the input
sensor reading buffer (if any), thus allowing to accumulate sensor
values with subsequent calls

- The MQTT topic of a sensor is now used to identify the file name of the
sink and is appended to the path given as input

- Template for Job Analyzers, derived from AnalyzerInterface

RESTHttpsServer: lower log level on socket shutdown to warning, as an error code does not necessarily indicate a problem

- Fixing a bug that caused endianness detection to not work properly
after switching to the new BOOST macros, causing dcdbquery and other
tools to break

- Analytics plugins can be now loaded and unloaded dynamically
- DCDBPusher now looks into the current configuration directory if no
path is supplied when loading/reloading a plugin

- Added a catch for an exception thrown when using on-demand analyzers
- Checking that the HTTPS server is actually running before stopping it in
the destructor

- String topics are now used across all of DCDB, up to Cassandra
- As of now, sensor names ALWAYS match MQTT topics
- Users can still define sensor "aliases" via dcdbconfig that point
to the same topics

CollectAgent should be switched to new Rest API design as soon as possible
Minor improvements to README, Makefile and PUT /analytics/reload methods

- Fixed name of log files for collectagent
- Fixed a few compilation warnings under gcc 7
- README for dcdbpusher now correctly refers to dcdbpusher.conf files
- SensorNavigator is rebuilt after plugin reloads only if data analytics
are currently running

- By convention, users should supply '.' characters instead of '/' when
querying sensor topics over the REST API to avoid conflicts with URL
parsing; the characters are then replaced automatically in the server

- Textual MQTT topics working in dcdbpusher and data analytics framework
- REST API still not working properly
- Testing on the collectagent not performed yet

- a "filter" configuration parameter has been added, which is used
to discard sensor names when building the sensor navigator
- Can be used to e.g. build a sensor navigator in a collectagent
using only the sensors that are directly collected by it
- Implemented a switch to select leftmost/rightmost binary search
in CacheEntry, used for the QueryEngine

- Parsing of host:port network addresses is handled by GlobalConfiguration
- -p dcdbpusher command line parameter (broker port) removed and integrated
into the -b argument