You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2018/01/10 00:05:00 UTC

[jira] [Created] (HIVE-18419) CliDriver loads different hive-site.xml into HiveConf and MetastoreConf

Eugene Koifman created HIVE-18419:
-------------------------------------

             Summary: CliDriver loads different hive-site.xml into HiveConf and MetastoreConf
                 Key: HIVE-18419
                 URL: https://issues.apache.org/jira/browse/HIVE-18419
             Project: Hive
          Issue Type: Bug
          Components: Test
    Affects Versions: 3.0.0
            Reporter: Eugene Koifman
            Assignee: Eugene Koifman


Various forms of CliDriver use CliConfigs to set the 'confDir' below  (e.g. CliConfigs.SparkOnYarnCliConfig() used by TestMiniSparkOnYarnCliDriver.


QTestUtil.QTestUtil() has
{noformat}
    if (confDir != null && !confDir.isEmpty()) {
      HiveConf.setHiveSiteLocation(new URL("file://"+ new File(confDir).toURI().getPath() + "/hive-site.xml"));
      MetastoreConf.setHiveSiteLocation(HiveConf.getHiveSiteLocation());
      System.out.println("Setting hive-site: "+HiveConf.getHiveSiteLocation());
    }
{noformat}

This causes HiveConf.initialize() to load hvie-site.xml from that location.

MetastoreConf only loads hive-site.xml from the classpath which in the test environment picks up data/conf/hive-site.xml

So different parts of the system may end up disagreeing about property values.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)