--On Sunday, January 29, 2006 2:32 AM -1000 "(Cedric) Qin ZHANG"
<[EMAIL PROTECTED]> wrote:
Hi, Philip,
The biggest problem with incremental data is that you don't how many days
you need to scan back (while doing analysis) when you want to have all
open issues for a particular day. This is necessary if you want to
calculate the number of issues satisfying certain criteria (e.g. open,
major issues in 7.3 release assigned to Philip). Unless "IssueSnapShot"
can anticipate all criteria we might need in the future, we have to
either (1) scan all the way back to day 0, or (2) make arbitrary decision
regarding how many days we need to go back.
Yes, this is true; I forgot to mention that issue. That's what the
IssueSnapshot SDT is supposed to overcome; any metric that requires
arbitrary look-back would be calculated on the server side.
I have a partial solution to reduce the amount of server side data. We
know that some sdt are "latest snapshot", such as Issue, Coverage. For
those types of data, we only need the latest batch. There could be a task
on the server side that wakes up daily to delete "non-latest" batches of
snapshot data.
But if we only had the latest snapshot, we couldn't do telemetry, so that's
probably not a good idea.
Cheers,
Philip
