Red Hat Bugzilla – Bug 494468
Filter on Cluster
Last modified: 2011-02-15 07:11:44 EST
Description of problem:
Currently you can enter a complete job ID in the search and it navigates to the specific job. e.g. you can enter 5.31 for job 5.31. It would be nice to just enter 5 and see the console filter on all jobs in the cluster 5.
I noticed this when doing the demo last week. I submitted a job and there were 000s of jobs before my cluster of jobs. I wanted to see the list without having to scroll to through. It would be nice to have a filter.
Might also be useful to have a cluster view. I.e. collapse all jobs in a cluster into one line. (??)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Also filter on user for admin to find a specific users jobs.
The core of this request, the part about focusing on just one cluster, is now addressed with submissions and the new navigation around them.
The other forms of filtering are, however, not addressed, and we unfortunately won't have time for them in 1.3. Moving this to 1.3.1.
Ernie has recently done work to support sql 'like' filtering on db-backed tables. To satisfy William's request, we'll need similar support on memory-backed tables.
Then, finally, we'll need to deploy a specific filter control for cluster on jobs. Ernie, sending this one your way.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
When cumin displays long lists of items spread across multiple pages, it is difficult to find a specific item or group of items.
The ability to search a list of items was added. The search term can appear anywhere in the search field.
fixed in cumin 4440. Available in build 4444.
Verified - cumin-0.1.4451-1.el5
Verified with cumin-0.1.4494-1.el5 as well
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.