Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 166098

Summary: CSV Log Report: extendedDataElements' values are missing, creationTime is the same for all events
Product: z_Archived Reporter: Jane Fang <janefang>
Component: TPTP.monitoringAssignee: Eugene Chan <ewchan>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P1 CC: rohit.shetty
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Patch to fix the extendedPr4operties and the multi-line problems
none
Zipped log file used to test the report generation.... none

Description Jane Fang CLA 2006-11-28 13:59:06 EST
1. import the log attached
2. generate a CSV log report
3. open the report with Excel
4. for those events that have extendedDataElements, only names show in the report, values are missing
5. and creationTime is the same after being converted to long and then presented in exponential format
Comment 1 Dave Smith CLA 2007-02-06 13:39:57 EST
Targetting this for iteration 2 and reassigning to Eugene to track this.  Additional resource can be applied to this defect if necessary. 
Comment 2 Rohit Shetty CLA 2007-03-03 02:38:42 EST
There are two problems which Jane describes here:
1) for those events that have extendedDataElements, only names show in the
report, values are missing

2) and creationTime is the same after being converted to long and then
presented in exponential format


On the second problem, creationTime being the same for all the records i could not simulate the problem. The problem is with the configuration in Excel. If you select the column and go to "Format Cell" on the menu and increase the number of decimal places you will see the complete time. This problem is basically with Excel trying to truncate the time during display. The CSV report has the correct and complete time generated and stored.
Comment 3 Rohit Shetty CLA 2007-03-03 02:47:18 EST
For the first problem described by Jane it seems like the report was coded so that only the extendedDataElement name was added to the report and its values were ignored. 

Eugene,
     is this done intentionally? I dont see a reason why this should be so!!!

Comment 4 Rohit Shetty CLA 2007-03-07 14:29:39 EST
i found A problem with the formatting when the msg has multiple lines. We should be handling this special case by putting the string inside double quotes without which the records are not displayed correctly in excel.
Comment 5 Rohit Shetty CLA 2007-03-07 14:32:32 EST
Created attachment 60393 [details]
Patch to fix the extendedPr4operties and the multi-line problems

The fixes exist in the file org.eclipse.tptp.platform.la.core\cbe\org\eclipse\tptp\monitoring\log\provisional\export\CSVExportHandler.java

The fix handles the senario of multiple extendedProperties as well as multiple levels of extended properties.

Please review the patch and let me know if any changes are required. Thanks!!!
Comment 6 Rohit Shetty CLA 2007-03-07 14:36:21 EST
Created attachment 60395 [details]
Zipped log file used to test the report generation....

I used the following log file to test the proposed fix. It has multiple extended properties and multiple levels of extendedProperties.

It can also be used to test the problem with multiple lines  that i described earlier.
Comment 7 Eugene Chan CLA 2007-03-22 19:43:47 EDT
Patch is submitted. [NCC] Rohit Shetty, rohit.shetty@in.ibm.com
Comment 8 Jane Fang CLA 2007-05-08 16:58:35 EDT
verified