You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Bruno Pusztahazi (JIRA)" <ji...@apache.org> on 2019/05/20 10:54:00 UTC
[jira] [Created] (HIVE-21754) Metastore schema different precision
can cause comparision issues
Bruno Pusztahazi created HIVE-21754:
---------------------------------------
Summary: Metastore schema different precision can cause comparision issues
Key: HIVE-21754
URL: https://issues.apache.org/jira/browse/HIVE-21754
Project: Hive
Issue Type: Bug
Components: Metastore
Affects Versions: 3.0.0
Reporter: Bruno Pusztahazi
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:
{code:java}
EXPECTED: ['avg_col_len','1.9802'], ACTUAL: ['avg_col_len','1.9802041447571914']{code}
Preferably all schemas should use the same precision data types.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)