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

[Kenny Gryp]

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)]

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)]

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

[Shahriyar Rzayev (rzayev-sehriyar)]

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