He has a point though, why go to the trouble of removing the data to tell that a job is no longer active, when there's a field that tells us if the job is active? Was there some other reason?
On Tue, Jul 2, 2013 at 4:42 PM, Kelven Yang <kelven.y...@citrix.com> wrote: > Fields in job record are tend to be used to reflect job status in job's > life cycle instead of history. > > Kelven > > On 7/2/13 1:35 PM, "Ryan Dietrich" <r...@betterservers.com> wrote: > >>Ok. I see the "reset attached object" calls now. >> >>I'm curious why those columns are being wiped out. If you wanted to see >>outstanding calls for an ID or Type, wouldn't you just query where the >>jobStatus is still equal to zero? >> >>Wiping out those columns seems to destroy history, no? >> >>On Jul 2, 2013, at 2:27 PM, Alena Prokharchyk >><alena.prokharc...@citrix.com> wrote: >> >>> Ryan, >>> >>> Those fields were added to indicate the instances (volumes, vms, etc) >>> having pending/active async jobs. The customers' main use case was - by >>> instance id, find out the jobs that are currently being executed for >>>this >>> instance. Once the job is completed, the field is offset to NULL. >>> >>> -Alena. >> >
