| Summary: | Bad type of value of some keys in job Classads from Aviary | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Daniel Horák <dahorak> |
| Component: | condor-aviary | Assignee: | Pete MacKinnon <pmackinn> |
| Status: | CLOSED NOTABUG | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | Development | CC: | matt |
| Target Milestone: | 2.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-05 21:02:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Daniel Horák
2011-10-05 14:42:24 UTC
This behaviour is by design. Aviary carries a different type encoding in its API which is more general. The cases where the QMF API gets tangled up is in the representation of Condor ClassAd expressions. In QMF, these have to be denoted out-of-band using a verbose descriptor tag. Aviary addresses this by treating every attribute value as a string with an accompanying type enumeration. These enumerations are FLOAT, INTEGER, EXPRESSION, BOOLEAN, etc. Also, note that there is no requirement that Aviary and QMF have parity in their type encoding of ClassAd values (just that the type can be inferred or declared), so not sure what this test is all about. |