org.apache.brooklyn.rest.resources

Class EntityResource.InterestingTasksFirstComparator

java.lang.Object

org.apache.brooklyn.rest.resources.EntityResource.InterestingTasksFirstComparator

All Implemented Interfaces:

java.util.Comparator<Task<?>>

Enclosing class:

EntityResource

public static class EntityResource.InterestingTasksFirstComparator
extends java.lang.Object
implements java.util.Comparator<Task<?>>

API does not guarantee order, but this is a the one we use (when there are lots of tasks): prefer top-level tasks and to recent tasks, balanced such that the following are equal:

something manually submitted here, submitted two hours ago something submitted from another entity, submitted ten minutes ago anything in progress, submitted one minute ago anything not started, submitted ten seconds ago anything completed, submitted one second ago

So if there was a manual "foo" effector invoked via REST on this entity a day ago, a "bar" effector invoked from a parent effector would only be preferred if invoked in the last two hours; active subtasks of "bar" would be preferred if submitted within the last 12 minutes, unstarted subtasks if submitted within 2 minutes, and completed subtasks if within the last 12 seconds. Thus there is a heavy bias over time to show the top-level tasks, but there is also a bias for detail for very recent activity.

It's far from perfect but provides a way -- when there are lots of tasks -- that we can show important things, where important things are the top level and very recent.