You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2014/10/25 23:14:33 UTC
[jira] [Created] (HIVE-8605) HIVE-5799 breaks backward
compatibility for time values in config
Alan Gates created HIVE-8605:
--------------------------------
Summary: HIVE-5799 breaks backward compatibility for time values in config
Key: HIVE-8605
URL: https://issues.apache.org/jira/browse/HIVE-8605
Project: Hive
Issue Type: Bug
Components: Configuration
Affects Versions: 0.14.0
Reporter: Alan Gates
Assignee: Alan Gates
Priority: Blocker
Fix For: 0.14.0
It is legal for long values in the config file to have an L or for float values to have an f. For example, the default value for hive.compactor.check.interval was 300L. As part of HIVE-5799, many long values were converted to TimeUnit. Attempts to read these values now throw "java.lang.IllegalArgumentException: Invalid time unit l"
We need to change this to ignore the L or f, so that users existing config files don't break. I propose to do this by changing HiveConf.unitFor to detect the L or f and interpret it to mean the default time unit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)