Branch: refs/heads/implicit-tenants Home: https://github.com/hawkular/hawkular-metrics Commit: b0766011f88c679fcfc62274df02d1497dc74b78 https://github.com/hawkular/hawkular-metrics/commit/b0766011f88c679fcfc62... Author: John Sanda <jsanda(a)redhat.com&gt; Date: 2015-08-17 (Mon, 17 Aug 2015) Changed paths: M api/metrics-api-jaxrs/src/main/java/org/hawkular/metrics/api/jaxrs/MetricsServiceLifecycle.java M core/metrics-core-impl/src/main/java/org/hawkular/metrics/core/impl/CreateTenants.java M core/metrics-core-impl/src/main/java/org/hawkular/metrics/core/impl/DateTimeService.java M core/metrics-core-impl/src/main/java/org/hawkular/metrics/core/impl/MetricsServiceImpl.java M rest-tests/src/test/groovy/org/hawkular/metrics/rest/CountersITest.groovy M rest-tests/src/test/groovy/org/hawkular/metrics/rest/RESTTest.groovy M rest-tests/src/test/groovy/org/hawkular/metrics/rest/TenantITest.groovy M task-queue/src/main/java/org/hawkular/metrics/tasks/api/AbstractTrigger.java M task-queue/src/main/java/org/hawkular/metrics/tasks/api/RepeatingTrigger.java Log Message: ----------- [HWKMETRICS-204] update tenants_by_time when inserting data, add REST API test We now update the tenants_by_time table when inserting gauge data points. There is also a REST API test to verify that the tenant is created when we only insert gauge data points without explicitly creating the tenant. I will add logic/tests for availability and counters in subsequent commits. MetricsServiceLifecycle has also been updated to initialize scheduled jobs, which now include the GenerateRate and CreateTenants classes. I do not like having the job initialization logic, particularly the part of subscribing the jobs, in MetricsServiceLifecyle. It should be a separate, core concern IMO. This will probably be refactored in the near future once we see how the scheduled jobs takes shape.