You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/04/22 04:55:59 UTC

[jira] [Commented] (AMBARI-10646) HBase config UI: Eliminate hbase.client.scanner.caching setting

    [ https://issues.apache.org/jira/browse/AMBARI-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506306#comment-14506306 ] 

Srimanth Gunturi commented on AMBARI-10646:
-------------------------------------------

Tests pass locally. Failures are for unrelated functionality
{code}

Results :

Tests in error:
  test220Cardinality(org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest): Guice provision errors:(..)
  test220AutoDeploy(org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest): Guice provision errors:(..)
  test220Dependencies(org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest): Guice provision errors:(..)

Tests run: 2875, Failures: 0, Errors: 3, Skipped: 17

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 43:50.179s
[INFO] Finished at: Tue Apr 21 19:54:30 PDT 2015
[INFO] Final Memory: 27M/476M
[INFO] ------------------------------------------------------------------------
{code}

> HBase config UI: Eliminate hbase.client.scanner.caching setting
> ---------------------------------------------------------------
>
>                 Key: AMBARI-10646
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10646
>             Project: Ambari
>          Issue Type: Task
>          Components: contrib
>    Affects Versions: 2.1.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 2.1.0
>
>
> After more research on this, the main way to configure this has changed to a different variable. For now we want to eliminate the setting completely. We can revisit the right approach some other time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)