Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
COSMOS Design 214794
Back to Data Reporting Design
Contents
Change History
| Name: | Date: | Revised Sections: |
|---|---|---|
| Sheldon Lee-Loy | 01/09/2008 |
|
Workload Estimation
| Process | Sizing | Names of people doing the work |
|---|---|---|
| Design | 0.2 | Sheldon Lee-Loy |
| Code | 3 | |
| Test | 0.5 | |
| Documentation | 0.5 | |
| Build and infrastructure | 0.2 | |
| Code review, etc.* | ||
| TOTAL | 3.4 |
'* - includes other committer work (e.g. check-in, contribution tracking)
Purpose
A generic cmdbf query builder will provide a convinient way for users to construct cmdbf queries. The query builder should provide extension points to allow the customization of the builder.
The service meta-data introduced in CMDBf1.0 can be used in this case to prompt the user with only what is supported by an MDR. In case an MDR does not provide meta-data, then all constraints should be enabled. The meta-data can be used to determine
1. Support for relationship cardinality and depth limit 2. Support for constraints 3. The operators supported on a property value constraint 4. XPath dialect support 5. Record types supported
As a result the generic query builder should query the MDR to determine what kinds of query the user can build.
Design
The initial focus of this design should support all query directives. As a stretch goal the query builder can query an MDR for meta data information.
Mockups
Open Issues/Questions
All reviewer feedback should go in the Talk page for 214794.