GitLab

Make sure the Runnable dies if it did not receive all the expected data (instead of producing an incorrect result)

It is no longer necessary, because adding the Analyses is actually not symmetrical:
collections of the "native" pipeline know about the newly added objects,
but these objects still refer to their "foreign" hive_pipeline, which makes it possible
to derive their original AnalysisStats dynamically.
Keep this in mind until adding these objects is no longer necessary (desired redesign plan).

* version/2.3:
  Don't need %hash_interval, can simply use %hash_curr_workers
  bugfix: make sure the plot start exactly at $start_date
  Decreased the threshold for detecting rounding errors. This allows to show memory usage as low as 5Mb
  bugfix: alive workers are now displayed until the current time

* version/2.2:
  Don't need %hash_interval, can simply use %hash_curr_workers
  bugfix: make sure the plot start exactly at $start_date
  Decreased the threshold for detecting rounding errors. This allows to show memory usage as low as 5Mb
  bugfix: alive workers are now displayed until the current time

cherry picked from commit master - bcd6efd7 and bugfixed
again to correctly initialize the first data-point

Decreased the threshold for detecting rounding errors. This allows to show memory usage as low as 5Mb

(cherry picked from commit 62ab80ed)

(cherry picked from master - commit 2c788dfd)

introduced TheApiary as the collection of collections and a central find_by_url() method for foreign objects

list_all_hive_tables/views can only be called on a eHive DBA, i.e. on a Hive database (recognized by the "hive_meta" table)