[kepler-dev] [Bug 5319] New: 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

           Summary: The workflow which archive sensor data into metacat
                    can upload incorrect data set when new data is coming
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sensor-view
        AssignedTo: barseghian at nceas.ucsb.edu
        ReportedBy: tao at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


I used sensor simulator to create data set, then killed the simulator. It
created data with timestamp from  2011-02-22 03:16:54 to 2011-02-22 03:17:52.

I ran the workflow and got the eml has the title:
Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22
03:16:54" and "2011-02-22 03:17:52"

I checked the data file in metacat and it has the data
from 2011-02-22 03:16:54 to 2011-02-22 03:17:52

Everything looks good. 

Then I ran the sensor simulator again and created some new data. Then I killed
the simulator. It created data with timestamp from 2011-02-22 03:57:35 to
2011-02-22 03:58:33

I ran the workflow again and two eml documents were uploaded:
1. Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22
03:16:54" and "2011-02-22 03:58:33"

2. Dataset for sensor:"sensor0" at site:"gpp" for time period "2011-02-22
03:57:35" and "2011-02-22 03:58:33"

I double checked the data file in metacat and found the data files comply with
the metadata.

>From the title, we can see the dataset 1 combines both dataset 2 and the
previous dataset which was uploaded in the last time.

So we have the duplicated data. The second run should only create the dataset
2.

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