Bug 1042266 - [RFE][ceilometer]: Complex filter expressions in API queries
Summary: [RFE][ceilometer]: Complex filter expressions in API queries
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Upstream M3
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/ceil...
Whiteboard: upstream_milestone_icehouse-3 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:35 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-19 15:29:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 21:35:03 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ceilometer/+spec/complex-filter-expressions-in-api-queries.

Description:

The current version of the API supports only the AND relation between the fields of the query filters. The idea is to provide the possibility to use both AND and OR relations and build complex filtering expressions with them.

In order to support these complex filters:
* a query grammar should be defined, which 
** satisfies the current needs
** is extendable to include further demands later
* the complex filter expressions should be convertible into JSON strings
* POST requests have to be used instead of GET, to be able to send the JSON query filter string in the body of the request
* consider the creation of a new REST resource for queries 
** to avoid the difficulties during the modification of the current solution 
** keep the API as simple and modular as possible
* choose a DB driver for a proof of concept implementation

The etherpad with further details and comments, can be found here:
https://etherpad.openstack.org/p/Ceilometer_extended_API_query_filtering


Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.