pt-query-digest should detect --type, or bail out if the wrong one is given

Bug #875895 reported by Kenny Gryp on 2011-10-16
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Invalid
Undecided
Unassigned

Bug Description

It did happen to me that I chose the wrong --type with pt-query-digest.
If you're processing a large file, pt-query-digest might start using a lot of memory and only show you at the end of the processing that no events have been processed.

It would be a good feature to be safe and bail out when the wrong type is given, or detect the type automatically.

Baron Schwartz (baron-xaprb) wrote :

I think that we can consider implementing automatic type detection in
the same way I did for the multi-layered parsing for syslog + postgres
logs. This is complex to implement, though.

Daniel Nichter (daniel-nichter) wrote :

This is a feature more than a bug so I made a skeleton spec for it: https://blueprints.launchpad.net/percona-toolkit/+spec/detect-log-type

Changed in percona-toolkit:
status: New → Invalid

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-885

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers