You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The current implementation of MetricPredicate translate to a query that consider the Datastore Schema. Specifically, an example MetricPredicate would translate to JSON as
This means that filtering for a metric type and/or value would always return 0 entries
To Reproduce
Steps to reproduce the behavior:
Perform a REST call to /{scopeId}/dataMessages filtering on metricName, metricType, metricMin and metricMax
Expected behavior
A set of results matching the name, type and values would return
Version of Kapua
1.0.9
1.1.2
Type of deployment
[x] Local Vagrant deployment
[x] Docker
[x] Openshift (in its variants)
[x] Others
Main component affected
[ ] Console (in case of console please report info on which browser you encountered the problem)
[x] REST API
[ ] Message Broker
[x] - Others
Additional context
Basically any component that uses di ES REST client is affected
The text was updated successfully, but these errors were encountered:
Describe the bug
The current implementation of
MetricPredicate
translate to a query that consider the Datastore Schema. Specifically, an exampleMetricPredicate
would translate to JSON asWhile it should translate to this JSON to support our current schema:
This means that filtering for a metric type and/or value would always return 0 entries
To Reproduce
Steps to reproduce the behavior:
/{scopeId}/dataMessages
filtering onmetricName
,metricType
,metricMin
andmetricMax
Expected behavior
A set of results matching the name, type and values would return
Version of Kapua
1.0.9
1.1.2
Type of deployment
[x] Local Vagrant deployment
[x] Docker
[x] Openshift (in its variants)
[x] Others
Main component affected
[ ] Console (in case of console please report info on which browser you encountered the problem)
[x] REST API
[ ] Message Broker
[x] - Others
Additional context
Basically any component that uses di ES REST client is affected
The text was updated successfully, but these errors were encountered: