FAQ
I'm fairly familiar with the CDH stack, but have only been a CDM convert
for the past couple of months. We're running on AWS, and recently we've
decided to downgrade our cluster. This required shifting roles across
different instances, and in the mix Hue no longer starts. Looking into the
manager logs, I've found the following stacktrace but not sure how to
proceed without digging into the source. I've tried resetting the
configuration to defaults as well as creating a new service from scratch,
but the error remains. (The error is observed for both the hue server and
beeswax server roles.)

Any suggestions?
-James

Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable to
generate config file hue.ini for role with type HUE_SERVER: null
         at
com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
         at
com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
         at
com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
         at
com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
         at
com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
         ... 90 more
Caused by: java.lang.IllegalStateException
         at
com.google.common.base.Preconditions.checkState(Preconditions.java:133)
         at
com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
         at
com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
         at
com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
         at
com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
         at
com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
         at
com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
         at
com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
         at
com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
         at
com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)

Search Discussions

  • Vikram Srivastava at Jun 10, 2013 at 10:04 pm
    Hue requires a Namenode or an Httpfs role to run. Make sure that the role
    that HDFS Web Interface Role config on Hue service's config page points to
    still exists.
    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM convert
    for the past couple of months. We're running on AWS, and recently we've
    decided to downgrade our cluster. This required shifting roles across
    different instances, and in the mix Hue no longer starts. Looking into the
    manager logs, I've found the following stacktrace but not sure how to
    proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable to
    generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)
  • James Warren at Jun 10, 2013 at 10:26 pm
    Thanks for the quick feedback. I earlier discovered posts where others
    encountered similar difficulties and believe this situation is different.
      To confirm, I've posted the a snapshot of the relevant part of my config:

    http://imageshack.us/f/94/hueconf.png/

    And just to cover all the bases, yes, my namenode is active when attempting
    to launch Hue. (All other parts of my hadoop stack are online.)

    Any other suggestions?

    Thanks,
    -James
    On Mon, Jun 10, 2013 at 3:03 PM, Vikram Srivastava wrote:

    Hue requires a Namenode or an Httpfs role to run. Make sure that the role
    that HDFS Web Interface Role config on Hue service's config page points
    to still exists.

    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM convert
    for the past couple of months. We're running on AWS, and recently we've
    decided to downgrade our cluster. This required shifting roles across
    different instances, and in the mix Hue no longer starts. Looking into the
    manager logs, I've found the following stacktrace but not sure how to
    proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable to
    generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)
  • Vikram Srivastava at Jun 10, 2013 at 10:41 pm
    A few other things to check:
    1. Hue server and Beeswax server are co-located
    2. Post a screenshot of what happens when you try to start hue service. You
    should see a popup for "Start" command. Let it finish and paste the popup.
    3. If you are using CM 4.5, there is a small flag at the top right that
    says "Configuration Validations". Make sure it doesn't have a number in a
    red box (signalling config error).
    On Mon, Jun 10, 2013 at 3:25 PM, James Warren wrote:

    Thanks for the quick feedback. I earlier discovered posts where others
    encountered similar difficulties and believe this situation is different.
    To confirm, I've posted the a snapshot of the relevant part of my config:

    http://imageshack.us/f/94/hueconf.png/

    And just to cover all the bases, yes, my namenode is active when
    attempting to launch Hue. (All other parts of my hadoop stack are online.)

    Any other suggestions?

    Thanks,
    -James
    On Mon, Jun 10, 2013 at 3:03 PM, Vikram Srivastava wrote:

    Hue requires a Namenode or an Httpfs role to run. Make sure that the role
    that HDFS Web Interface Role config on Hue service's config page points
    to still exists.

    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM convert
    for the past couple of months. We're running on AWS, and recently we've
    decided to downgrade our cluster. This required shifting roles across
    different instances, and in the mix Hue no longer starts. Looking into the
    manager logs, I've found the following stacktrace but not sure how to
    proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable to
    generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)
  • Vikram Srivastava at Jun 10, 2013 at 10:46 pm
    Also, 4. your oozie service has an Oozie server instance.
    On Mon, Jun 10, 2013 at 3:41 PM, Vikram Srivastava wrote:

    A few other things to check:
    1. Hue server and Beeswax server are co-located
    2. Post a screenshot of what happens when you try to start hue service.
    You should see a popup for "Start" command. Let it finish and paste the
    popup.
    3. If you are using CM 4.5, there is a small flag at the top right that
    says "Configuration Validations". Make sure it doesn't have a number in a
    red box (signalling config error).

    On Mon, Jun 10, 2013 at 3:25 PM, James Warren wrote:

    Thanks for the quick feedback. I earlier discovered posts where others
    encountered similar difficulties and believe this situation is different.
    To confirm, I've posted the a snapshot of the relevant part of my config:

    http://imageshack.us/f/94/hueconf.png/

    And just to cover all the bases, yes, my namenode is active when
    attempting to launch Hue. (All other parts of my hadoop stack are online.)

    Any other suggestions?

    Thanks,
    -James
    On Mon, Jun 10, 2013 at 3:03 PM, Vikram Srivastava wrote:

    Hue requires a Namenode or an Httpfs role to run. Make sure that the
    role that HDFS Web Interface Role config on Hue service's config page
    points to still exists.

    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM
    convert for the past couple of months. We're running on AWS, and recently
    we've decided to downgrade our cluster. This required shifting roles
    across different instances, and in the mix Hue no longer starts. Looking
    into the manager logs, I've found the following stacktrace but not sure how
    to proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable
    to generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)
  • James Warren at Jun 10, 2013 at 11:12 pm
    Thanks for the info - it was indeed #4. As a recommendation, could you add
    some additional logging to the process? It's not apparent that Oozie
    should be a prerequisite for Hue, and getting a null exception in this case
    wasn't exactly enlightening!

    cheers,
    -James
    On Mon, Jun 10, 2013 at 3:46 PM, Vikram Srivastava wrote:

    Also, 4. your oozie service has an Oozie server instance.

    On Mon, Jun 10, 2013 at 3:41 PM, Vikram Srivastava wrote:

    A few other things to check:
    1. Hue server and Beeswax server are co-located
    2. Post a screenshot of what happens when you try to start hue service.
    You should see a popup for "Start" command. Let it finish and paste the
    popup.
    3. If you are using CM 4.5, there is a small flag at the top right that
    says "Configuration Validations". Make sure it doesn't have a number in a
    red box (signalling config error).

    On Mon, Jun 10, 2013 at 3:25 PM, James Warren wrote:

    Thanks for the quick feedback. I earlier discovered posts where others
    encountered similar difficulties and believe this situation is different.
    To confirm, I've posted the a snapshot of the relevant part of my config:

    http://imageshack.us/f/94/hueconf.png/

    And just to cover all the bases, yes, my namenode is active when
    attempting to launch Hue. (All other parts of my hadoop stack are online.)

    Any other suggestions?

    Thanks,
    -James

    On Mon, Jun 10, 2013 at 3:03 PM, Vikram Srivastava <vikrams@cloudera.com
    wrote:
    Hue requires a Namenode or an Httpfs role to run. Make sure that the
    role that HDFS Web Interface Role config on Hue service's config page
    points to still exists.

    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM
    convert for the past couple of months. We're running on AWS, and recently
    we've decided to downgrade our cluster. This required shifting roles
    across different instances, and in the mix Hue no longer starts. Looking
    into the manager logs, I've found the following stacktrace but not sure how
    to proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable
    to generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)
  • Vikram Srivastava at Jun 10, 2013 at 11:40 pm
    We apologize for the inconvenience. Your request has been duly noted and
    will be fixed in an upcoming release.
    On Mon, Jun 10, 2013 at 4:12 PM, James Warren wrote:

    Thanks for the info - it was indeed #4. As a recommendation, could you
    add some additional logging to the process? It's not apparent that Oozie
    should be a prerequisite for Hue, and getting a null exception in this case
    wasn't exactly enlightening!

    cheers,
    -James

    On Mon, Jun 10, 2013 at 3:46 PM, Vikram Srivastava wrote:

    Also, 4. your oozie service has an Oozie server instance.

    On Mon, Jun 10, 2013 at 3:41 PM, Vikram Srivastava wrote:

    A few other things to check:
    1. Hue server and Beeswax server are co-located
    2. Post a screenshot of what happens when you try to start hue service.
    You should see a popup for "Start" command. Let it finish and paste the
    popup.
    3. If you are using CM 4.5, there is a small flag at the top right that
    says "Configuration Validations". Make sure it doesn't have a number in a
    red box (signalling config error).

    On Mon, Jun 10, 2013 at 3:25 PM, James Warren wrote:

    Thanks for the quick feedback. I earlier discovered posts where others
    encountered similar difficulties and believe this situation is different.
    To confirm, I've posted the a snapshot of the relevant part of my config:

    http://imageshack.us/f/94/hueconf.png/

    And just to cover all the bases, yes, my namenode is active when
    attempting to launch Hue. (All other parts of my hadoop stack are online.)

    Any other suggestions?

    Thanks,
    -James

    On Mon, Jun 10, 2013 at 3:03 PM, Vikram Srivastava <
    vikrams@cloudera.com> wrote:
    Hue requires a Namenode or an Httpfs role to run. Make sure that the
    role that HDFS Web Interface Role config on Hue service's config page
    points to still exists.

    On Mon, Jun 10, 2013 at 3:00 PM, James Warren wrote:

    I'm fairly familiar with the CDH stack, but have only been a CDM
    convert for the past couple of months. We're running on AWS, and recently
    we've decided to downgrade our cluster. This required shifting roles
    across different instances, and in the mix Hue no longer starts. Looking
    into the manager logs, I've found the following stacktrace but not sure how
    to proceed without digging into the source. I've tried resetting the
    configuration to defaults as well as creating a new service from scratch,
    but the error remains. (The error is observed for both the hue server and
    beeswax server roles.)

    Any suggestions?
    -James

    Caused by: com.cloudera.cmf.service.config.ConfigGenException: Unable
    to generate config file hue.ini for role with type HUE_SERVER: null
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:47)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigsPlus(HandlerUtil.java:179)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:146)
    at
    com.cloudera.cmf.service.HandlerUtil.generateConfigs(HandlerUtil.java:111)
    at
    com.cloudera.cmf.service.AbstractRoleHandler.generateConfiguration(AbstractRoleHandler.java:513)
    ... 90 more
    Caused by: java.lang.IllegalStateException
    at
    com.google.common.base.Preconditions.checkState(Preconditions.java:133)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.getTargetRole(HostNameEvaluator.java:152)
    at
    com.cloudera.cmf.service.config.HostNameEvaluator.evaluateConfig(HostNameEvaluator.java:218)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.CombinedEvaluator.evaluateConfig(CombinedEvaluator.java:107)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.HueConfigSectionEvaluator.evaluateConfig(HueConfigSectionEvaluator.java:60)
    at
    com.cloudera.cmf.service.config.AbstractConfigEvaluator.evaluateConfig(AbstractConfigEvaluator.java:70)
    at
    com.cloudera.cmf.service.config.ConfigGeneratorHelpers.generateOptionsFromEvaluators(ConfigGeneratorHelpers.java:78)
    at
    com.cloudera.cmf.service.config.HueConfigFileGenerator.generate(HueConfigFileGenerator.java:43)

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJun 10, '13 at 10:00p
activeJun 10, '13 at 11:40p
posts7
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Vikram Srivastava: 4 posts James Warren: 3 posts

People

Translate

site design / logo © 2022 Grokbase