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

- 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

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

- Allows to quit the collectagent or dcdbpusher with a specified return code.

Allow for actual configuration files to be specified on command line, not just configuration directories. Add exception handling to main of pusher, collectagent, grafanaserver

- New filtering methods applies a filtering regular expression to all
node names in the node list of a job; the mode of the filtered node names
is then computed, and the job is processed only if this matches an
arbitrary "match" string
- Can be used to assign jobs to different islands in a HPC system based
on the allocation of nodes

- Allows to reduce the size of the query results considerably

- Uses an overloaded version of the querySensor() method

- Implemented a (overloaded) publishSensor method in SensorConfig that
uses a SensorMetadata object to publish metadata selectively - only
columns that are set are updated, query statement is built on the fly
- Changing type of operations to set of strings still pending

- Allows to encode "not set" states for single members

-sends data as JSON to CollectAgent instead of storing in Cassandra directly
-adapt CA to support iob data

-CollectAgent and Pusher adapted for special handling of event data
-Handful of other fixes and improvements

- Especially useful in Collect Agent: now there is no need to restart
the CA to instantiate operator plugins after sensors have been
published

- Collectagent uses published TTL values and caches received metadata
- READMEs updated accordingly

- Also added a "pattern" field to SensorMetadata class for consistency
with the DCDB::PublicSensor class

- Metadata is now parsed from config files, sent from Pushers to
Collectagents as JSON, and finally written to Cassandra

- JSON metadata is sent only if a "metadata" block for the sensor is
defined, else if auto-publish is enabled we only send the sensor name

- Data is correctly parsed from DCDBPusher, sent as JSON, and received
by collectagents
- Integration in libdcdb is still pending

- Fixed a bug that prevented pipelines in collectagent deployments
- Incremented the tolerance threshold of fuzzy queries to 1h
- Fixed the assignment of MQTT topics to job sensors

- Fixed a bug that prevented relaxed mode from working properly for
operators deployed on the collectagent
- Changed the function of the "delay" parameter: it now specifies a
fixed offset applied to the computation interval of each operator,
useful to tune the flow of data in operator pipelines

- Now using references instead of pointers
- Return type is now bool

- If users specify a single timestamp (startTs==endTs) when performing
a sensor query through dcdbquery or libdcdb, a fuzzy sensor query is
performed, and the closest sensor reading to the target timestamp is
returned

- A regular expression (jobFilter) can be applied to the jobs' nodelists
to identify the jobs that need to be treated by each collectagent in a
cluster
- By default only the first node in the nodelist is considered, but this
behavior can be customized

- querySensor does not return NULL pointers anymore, but always
the "buffer" input argument
- the previous implementation was more descriptive of error statuses,
but much more prone to leaking memory in case of improper usage
- Also fixed a warning in the MSR plugin

- Fixed a bug in the collectagent that caused the QueryEngine to not
be treated correctly, due to a missing linking flag

- Make clean might be required