today we support "parent" and "grandparent" tokens. need to support at least two levels above that (great-grandparent and greatgreat-grandparent) use case is to aggregate the different GCs by name for particular JBossAS servers: resource.type.name = Garbage Collector // find all GC resources in inventory resource.type.plugin = JBossAS // which are found under JBoss server resource.greatGrandParent.name.contains = prod // but only whose JBAS ancestors are in prod groupby resource.name // create one group for each type ("Copy GC", "MarkSweepCompact GC", etc)
rev4573 (branch RHQ_1_1_0_GA_CP) - support two additional levels of ancestry-filtering for dynagroups
greatGrandParent, greatGreatGrandParent is not a scalable solution. Can we move to something like: ancestor[1]=parent ancestor[2]=grandparent ancestor[3]=greatGrandParent etc ancestor[n] even if its only a semantic change, this is more scalable syntax. We don't need to support arbitrary values of n, since that could require fundamental changes to how the backing sql is created. For a start lets just support upto n=4, since a quick look around a resource hierarchy only shows me resource with up to 4 levels of ancestors.
Moving features/improvements to 1.4
Move back to 1.3 if there is time to do this change since we put it in a CP
rev5090 - support two additional levels of ancestry-filtering for dynagroups: great-grandparent and great-great-grandparent; charles: i agree the "great-great" stuff isn't scalable. however, great-great-grand-parent is now supported, and that searches up 4 levels. my plan was definitely to do the ancestor[x] deal for this release, but forward-porting the fix took me probably 1/10 the time it would have taken to implement the ancestor fix. so, let's open a new jira if we still want the ancestor[x] solution, and we can put it on 1.4's plate.
test procedures are in the description, which includes the exact use case this feature was added for. also, make sure that "greatgrandparent" and "greatgreatgrandparent" are available in the dynagroup builder/wizard.
Tested the case in the description, which worked, see screenshot. rev5122
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2266 Imported an attachment (id=368763)