Metastore schema different precision can cause comparision issues

At least (but there could be others...) the avg_col_len statistic is defined with different data types in the schema for each sql flavor. This can cause comparison errors due to precision mismatch.

E.g. the mysql schema has explicit 4 digit precision ( double(53,4) ) defined while the postgres has DOUBLE PRECISION type which has a much longer precision.

This can cause issues like:

EXPECTED: ['avg_col_len','1.9802'], ACTUAL: ['avg_col_len','1.9802041447571914']

Preferably all schemas should use the same precision data types.