[kepler-dev] [Bug 5319] The workflow which archive sensor data into metacat can upload incorrect data set when new data is coming

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5319

--- Comment #3 from Jing Tao <tao at nceas.ucsb.edu> 2011-02-25 11:22:04 PST ---
This logic issue on two inputs, start time and interval, of DataTurbineActor 3.

The start time is using the current time, but the interval is using current
time - previous time. We change the start time is previous time and interval is
current time - previous time.

It works. Here is the result after running 3 times of the workflow:
1
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:05:24" and "2011-02-25 10:06:22"
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:06:24" and "2011-02-25 10:07:22"

2
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:07:22" and "2011-02-25 10:07:22"
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:07:24" and "2011-02-25 10:32:22"
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:32:24" and "2011-02-25 10:33:22"

3
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:33:22" and "2011-02-25 10:33:22"
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:33:24" and "2011-02-25 10:47:06"
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:47:08" and "2011-02-25 10:48:06"

But it still has issue on the boundary:
data with timestamp 2011-02-25 10:33:22 has been upload in the second time run:
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:32:24" and "2011-02-25 10:33:22

However, it was uploaded again in the third run:
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-25
10:33:22" and "2011-02-25 10:33:22"

You can see the document Dataset for sensor:"sensor0" at site:"gpp" for time
period "2011-02-25 10:33:22" and "2011-02-25 10:33:22" in the third run only
has a single data.

I dug around and found:

When lastUploadedTime 2011-02-25 10:33:22 was passed to DataTurbineActor 2,
three output came out:
2011-02-25 10:33:24
2011-02-25 10:47:07
2011-02-25 10:48:07

Actually there is not data or metadata with the timestamp 2011-02-25 10:33:24.
Is it a bug of DataTurbineActor?

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.