GitLab

- Job Operator job queries now use the timestamp for the next scheduled
invocation to define their time range
- Additional timestamp checks in PersystSQL

- Added a "raw" mode in which only the average is used as feature for
each sensor. Useful when users wish to build signatures with a different
plugin and then pipeline them into the model;
- Restored the "targetDistance" parameter for the Classifier plugin;
- Fixed a minor bug affecting the number of samples used for training.

- Fixed a memory leak
- Improved exception management
- General refactoring of the code

- Smoothing is not hardcoded anymore and the server picks automatically
the best smoother based on the available sensor operations
- Requires a "smootherRegex" configuration parameter to identify the
smoothing operations

- Caching metadata information
- Using a single persistent SensorDataStore instance
- Now properly querying multiple weekstamps if necessary

- Added all missing Cassandra configuration parameters
- Decoupled the sensor navigator's initialization
- Added the "filter" configuration parameter for the sensor navigator
- Improved error handling

- CA: sensors from job operators are not cached anymore
- CA: the analytics controller is now de-allocated properly
- Added a "tol" parameter to the QueryEngine interface for fuzzy queries

implementing metrics which go through smucngperf plugin, without transformations (basically only renaming), so that timestamps correspond with each other.

Allow for endTime != 0 for insertion into the jobData table if the last digit is 1 as set by dcdblsurmjob start

adding debug information, reducing the job cache, and optimizing the mysql query (only one query instead of two)