Logging options - full & reduced (suggestion)

[dfhtextpipe]

I have a suggestion for enhancing the use of logging options.

When several sub-filters use an external replace list file, and the files to be processed are numerous,
it often happens that for each such Replace filter, only one of the matching patterns needs to be replaced.
This is because the simplest way of replacing the same kind of item in each file, is to use such a list.

The consequence for the TextPipe log file is that it can end up including lots of lines like this:

Code: Select all

2013-05-06 09:55:27,Info,  1 replace(s) performed for pattern match [01]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [02]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [03]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [04]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [05]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [06]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [07]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [08]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [09]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [10]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [11]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [12]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [13]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [14]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [15]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [16]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [17]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [18]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [19]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [20]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [21]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [22]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [23]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [24]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [25]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [26]
2013-05-06 09:55:27,Info,  0 replace(s) performed for pattern match [27]

The log file would be less cluttered if Logging options were to have a feature to choose between Full or Reduced logging of such replace list filters.

Full logging would be the default, and behave as currently.
Reduced logging would log only the non-zero replaces performed for pattern matches in external replace list files.
A single check box in logging options would suffice to facilitate this de-cluttering.

Please review and comment. Thanks.

[DataMystic Support]

So you see it as an option of a search/replace list filter, and not of all pattern matches in the entire filter tree?

[dfhtextpipe]

That would be one way of implementing it, on a filter by filter basis.

Yet it might be rather more convenient to just have one single place in Filter options for the proposed check box,
with a clear explanation in the help file that it applies to all replace filters where the replace lists are an external file.

Whether there are other filters that use external files, for which reduced logging might be worth considering,
that's not something I've given much thought to.

David

[DataMystic Support]

If it only applies to the search/replace lists with an external file, then that's where it should go in the interface.

If it applied to all search/replaces with zero replacements, then it would go in the top level options. I think option 1) is the best place.

[dfhtextpipe]

OK - that's fine by me.

David

[DataMystic Support]

Hi David,

This has been built and tested for the v9.5 release this week.