| Summary: | Sensor attributre fileFooterSize should have a default value of zero | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Dave Smith <smith> |
| Component: | TPTP.monitoring | Assignee: | Alex Nan <apnan> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | labadie, rohit.shetty |
| Version: | unspecified | Keywords: | api, Documentation |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Dave Smith
This change will require a change in the documentation. Documentation is frozen for TPTP 4.0 so this change cannot be made until 4.1. Deferring this until a breaking API release because this change may break existing adapters that assume the default footer size is 90. This is required from the AC perspective. This bugzilla only affects adapters used in live log monitoring scenarios because fileFooterSize is only used when the context is configured with continuousOperation="true". In log import scenarios fileFooterSize is not used. The documentation file that needs to be updated for this change is: org.eclipse.tptp.monitoring.doc.isv/tasks/tconfiguresensor_rules.html I am adding a sizing of the work required: 1 hr - Updating the code and documentation 3 hrs - testing the existing TPTP adapters running in continuous live monitoring mode to ensure this change does not cause any regressions. 4 hrs total. As indicated in Comment #2 this change cannot be done until a breaking API release because it may cause existing adapters for logs that have a footer to no longer work properly in live monitoring mode. Reassigning defects to current component owner. No support for the GLA will be provided post 4.5. Closing. |