RTC attribute ID is case sensitive?
Hi All,
I have custom RTC attribute with ID "test_id" of type Iteration in one of work item type and later we added another attribute with ID "Test_Id" of enumeration type in same work item type. Now we don't use "test_id" Iteration attribute. so it will be unassigned all time.
I think some validation is done, while transferring data from LZ to IC. we see some rejected records in HDFS.
while validating it shows rejected records with these attribute names.
So is it problem with RTC - it doesn't handle 2 attribute having same ID with case difference.
Or validation check from LZ to IC needs any settings?
Please let me know what could be the direction resolve the issue.
Thanks,
Kavita
<o:p> </o:p> |
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Sep 19 '17, 10:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Sep 19 '17, 10:23 a.m. Yes, for all I know the attribute ID's are case sensitive and, in any case, you should always assume that ID values are case sensitive, because that is the quickest possible match. I would assume an information that they are not case sensitive in the rare cases where they aren't. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
could you please add more details on what it means to
transfer data from LZ to IC
and
how HDFS is involved here
Also, do you see any discrepancy in accessing the workitem in RTC clients... are you able to set these attributes Test_Id and test_id separately and are they retained correctly in RTC work item views.
From OSLC REST API perspective, the attributes are read and handled in a case sensitive way.. since RTC complies to OSLC CM Spec, we should be able to handle it as well.. based on the specific error you see, we can look further...
I don't have much information. But while transfering data from LZ(landing zone) to IC(Integrated Core) adds these ( WT and attribute name )details in log file