Release 0.7.6

[c0c0n3]

New features

• Save original data on translation error (Save original data on translation error #335)
• Make maximum number of rows a query can retrieve configurable (Port #319 changes to newly introduced sql translator class #330)
• Support CrateDB 4.x series (support crate 4.x #300)
• History of attributes from different entities with different types (API Implementation of /v2/attrs #294)
• Introduce support for log level configuration (introduce support for log level configuration #299)
• History of attributes from different entities of the same type (Added implementation for /v2/types/{entityType} #293)
• Make entities endpoint list IDs of all existing entities (Make /v2/entities return available ids. Fix for issue #162 #264)
• Move version, config and health endpoint to API root path (Fixed for #94 #261)

Bug fixes

• Log values of environment variables when reading them in (Log env var values when reading it them in #326)
• Reduce code duplication between CrateDB and Timescale translators; use UTC time consistently across the board for time indexing; fix date time SQL injection vulnerability (WIP: Fix 314 #315)
• Ignore attributes with null values (Fix issue#224 #298)
• Accept quoted values in API fromDate and toDate parameters (Fix for issue #225 #285)
• Use standard header names for FiWare service and service path (Fix for issue #148 #283)
• Update tests for incomplete entities to take into account changes introduced by PR Fix for Issue#209 #278 (Update test_incomplete_entities.py #282)
• Filter empty entities out of notification payload (Fix for Issue#209 #278)
• Pin Python/Alpine docker image to avoid dependency hell (fix #269 #271)
• Make /v2 return list of available API endpoints (Handling of ql/v2 root endpoint #255)
• Update network interface in Travis build (fix-breaking-travis-ci #260)
• Update FIWARE CSS to avoid redirect URL (Update FIWARE CSS to avoid redirect URL #252)

Documentation

• Update Japanese documentation to cater for CrateDB 4.x and environment variables ((ja) Update Japanese documents #333)
• Update contributors list (update credits #307)
• Remove "Migrating STH Comet data" manual section as no longer supported (Deleting dataMigration.md #267)
• Document data format expected by notify endpoint (Inserting data directly into Quantumleap #268)
• Timescale backend documentation (Timescale backend docs #263)
• Update Japanese documents ((ja) Update Japanese documents #280)
• Update broken link in in sanity check section of Japanese manual ((ja) Update hyper link in check.md (#289) #291)
• Updated broken links in sanity check section of manual (Updated broken links for check.md #289)
• Update broken links in CrateDB section of manual (Update broken links in reference to CrateDB #286)
• Update GitHub issue template (Update issue templates #259)
• State DB versions in README

Important: Backward compatibility

This release breaks API backward compatibility. Existing 0.7.5 clients may not be able to work with this new Quantum Leap version without code changes. In detail: version 0.7.6 changes the URL of the version, health and config endpoints as indicated below:

  0.7.5           0.7.6
  -----           -----
/v2/version      /version
/v2/config       /config
/v2/health       /health

Note that the semantics of the endpoints remains the same as version 0.7.5.

[c0c0n3]

@chicco785 should we release v 0.8 with this PR? i.e. should I complete the release notes and bump up the number returned by the version endpoint? Or should we hold off the release until we add more features?

[c0c0n3]

should we release v 0.8 with this PR

we're going to have an intermediate release instead (0.7.6) in preparation for 0.8. We'll release 0.8 when we're done implementing timescale queries---see #324.

[c0c0n3]

@chicco785 forcing the merge since it looks like Travis integration is broken on the GitHub side---if you click through you'll see all builds passed with flying colours but for some obscure reason the status on the GitHub side never gets updated from pending...