exact filtering of timestamps are useless, should be removed
Bug #1522322 reported by
Qiming Teng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| senlin |
Fix Released
|
High
|
Qiming Teng | ||
Bug Description
Currently profiles, policies and actions support an exact filtering based on created_time, updated_time and deleted_time.
These filters are useless, thus should be removed from the API interface.
In future, we can add more useful filters as suggested by api-wg, for timestamp related filtering.
| Changed in senlin: | |
| assignee: | nobody → Qiming Teng (tengqim) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to senlin (master) | #1 |
| Changed in senlin: | |
| status: | Triaged → Fix Committed |
| Changed in senlin: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/senlin 1.0.0.0b2 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit e6c20bec9b44a47
Author: tengqm <email address hidden>
Date: Thu Dec 3 20:32:28 2015 -0500
Remove timestamp fields from filtering parameters
The filtering logic (and grammar) today does not support complex ways
for specifying query conditions. This is something we need to improve.
However, current filter parameters still contain some timestamp fields,
on which the only filtering operation is '='. It is making these filters
not usable or even useless. This patch propose removing them. The
rationale is that once we have them in, we can NEVER deprecate them.
Change-Id: Id8ba28ef870e73
Closes-Bug: #1522322