Julien Danjou 502824ad2c api: allow usage of resource_metadata in query ...

When returning samples, they have a field called resource_metadata, and
therefore it may seem nature to filter on it using this as a prefix in
queries. Let's allow use of it.

Fixes-Bug: #1195765

Change-Id: I82f591e0d38a3063a9762de1ac64dc3ef9d29ee7

2013-08-26 10:37:42 +02:00

..

__init__.py

Implement V2 API with Pecan and WSME

2012-12-04 12:57:58 -05:00

base.py

api: enable v2 tests on SQLAlchemy & HBase

2013-06-21 11:19:58 +02:00

test_acl_scenarios.py

Change counter to sample vocable in api tests

2013-08-21 13:36:44 +02:00

test_alarm_scenarios.py

Bump hacking to 0.7.0

2013-08-16 13:22:03 +08:00

test_app.py

Merge "Add support for API message localization"

2013-08-09 14:00:56 +00:00

test_compute_duration_by_resource_scenarios.py

Add SQLAlchemy implementation of groupby

2013-08-19 04:56:16 +00:00

test_list_events_scenarios.py

Change counter to sample vocable in api tests

2013-08-21 13:36:44 +02:00

test_list_meters_scenarios.py

api: allow usage of resource_metadata in query

2013-08-26 10:37:42 +02:00

test_list_resources_scenarios.py

Change counter to sample vocable in api tests

2013-08-21 13:36:44 +02:00

test_post_samples_scenarios.py

message_id is not allowed to be submitted via api

2013-08-19 08:41:46 +02:00

test_query.py

Fixes non-string metadata query issue

2013-08-23 21:51:58 +08:00

test_statistics_scenarios.py

Change counter to sample vocable in api tests

2013-08-21 13:36:44 +02:00

test_statistics.py

api: enable v2 tests on SQLAlchemy & HBase

2013-06-21 11:19:58 +02:00