Comment 1 Christine Knight 2005-01-28 10:46:22 EST

Will provide more details soon.

Comment 2 Christine Knight 2005-01-28 14:18:46 EST

need to think more on this and break it down into a set of requirements based 
on a use case.

Comment 3 Dave Smith 2005-01-28 18:20:11 EST

Theme: Scaling Up

By reducing the amount of data that is parsed by the Parser component using 
regular expression parsing, the overall performance of GLA will be improved.

Further Description of Requirement:

The requirement is to allow the sensor or extractor to filter out lines or data 
that are not of interest, based on rules specified by the adapter writers 
and/or users.  More details of the use cases is required to size this 
feature.   

Comment 4 Dave Smith 2005-09-09 13:04:36 EDT

This new feature needs to be added to the documentation.

New messages will likely be required.

The GLA Editor will need to be regenerarted with new fields added to the GLA 
schema.

Comment 5 Dave Smith 2005-12-07 10:36:08 EST

Candidate for 4.2

Comment 6 Eric Labadie 2005-12-23 14:29:31 EST

After reviewing the design, here are my comments in upper case:
Use-case 1 (static, parser writer filtering)
... It is REQUIRED that the OSSingleFileSensor AND ANY OTHER GLA SENSORS/EXTRACTORS FROM TPTP currently included with TPTP GLA be changed to support regex filter specification as part of this feature. 
If both the filter specification and filter exit class is specified in the adapter, then the filter specification is passed to the filter exit class which then tests the log line based on the filter specification. 

Comment 7 Dave Smith 2006-02-13 02:31:20 EST

Created attachment 34557 [details]
Patch containing GLA code changes for this feature

Comment 8 Dave Smith 2006-02-13 02:34:48 EST

Committed code changes for this feature, as indicated in the attached patch file, to TPTP Head CVS.

The associated doc and GLA editor regeneration work will be completed under defects 127425 and 127428 respectively.

Comment 9 Paul Slauenwhite 2009-06-30 08:21:52 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.