How is modified_since in ETL mapped in ClearQuest?
![]()
I have an ETL for gathering data from ClearQuest. It works fine except for modified_since when a value of less than 6 hours is computed for the modified_since on the where clause of the defect query. I have defects that are say 1 or 2 hours old but if I use modified_since of 5:55 (H:mm) it returns 0 rows. If I use modified_since of 6:05 then the correct number of rows are returned. 6:00 also seems to fail as well. We have a requirement of being able to run the delta ETL every 6 hours in our environment. Since the ETL does take some time the modified_since will always be less than 6 hours and then it will fail. I am not the admin for CQ and don't they don't know what parameter needs to be change in their config to allow this to work - or is this a hard limitation in CQ?
|
2 answers
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.