Bugzilla – Full Text Bug Listing
| Summary: | Filtering doesn't work with child Additional Data Attribute values in large log support | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Rohit Shetty <rohit.shetty> |
| Component: | TPTP | Assignee: | Alex Nan <apnan> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | apnan, jkubasta, labadie, paul_gover, vsatpute |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
This is required from the AC perspective. I've just voted for this, on the (possibly incorrect) assumption that the problem I'm seeing is a duplicate. My problem is that the log viewer ignored filters on Message.Identifier and Message.CatalogId when in large log mode. (Sorry if the names are not 100% correct, but those are the fields.) These filters worked in XMI mode. I am pretty sure it's evaluating the filters, as there's a 10 - 30 second wait after I enter them (eg, Message.CatalogId=2233). The screen blinks as if it's been refreshed, but the contents have not been filtered, and I still have 18000 records displayed. This is on tje same environment as bug 216027. Just done some more testing, and can clarify what appears to be happening on my Message filters. If the filter matches 0 records, that's what I get. But if it matches any record, the log view displays all of them. I suspect either a Derby error, which seems unlikely, or an incorrectly-composed SQL selection where a join condition is matching too many records. Is not containable in i5, moving to i6. Re: to comment #3, the problem that you are seeing is for any CBE complex data types. This is more a feature then a defect and I'm not sure we will actually be able to contain it in i6 given the resources that we have. Retargetting to i8. Deferral to future with PMC approval No support will be provided for the Log and Trace Analyzer post 4.5. Closing. |
Build ID: I20070625-1500 Steps To Reproduce: Steps To Reproduce: 1. Import the attached log file (In large log mode), which contains child Additional Data Attribute Values. 2. Try to filter for child Additional Data Attribute "ValidationMessage" with filter definition: 'Additional Data Attribute Values' like 'Validating' 3. Filtering doesn't work for child Additional Data Attribute values. Expected Result: Filtering should work for child Additional Data Attributes also. More information: TPTP Build id: tptp.sdk-TPTP-4.4.0.1-200707090100 Sample log - https://bugs.eclipse.org/bugs/attachment.cgi?id=76873 More information: