[jira] [Commented] (AMBARI-21001) Hive 1.5.0 view does not load in Internet Explorer 11
[
https://issues.apache.org/jira/browse/AMBARI-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007645#comment-16007645
]
Hadoop QA commented on AMBARI-21001:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12867699/AMBARI-21001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[contrib/views/hive-next|https://builds.apache.org/job/Ambari-trunk-test-patch/11584//artifact/patch-work/testrun_hive-next.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11584//console
This message is automatically generated.
> Hive 1.5.0 view does not load in Internet Explorer 11
> -
>
> Key: AMBARI-21001
> URL: https://issues.apache.org/jira/browse/AMBARI-21001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk, 2.5.1
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: trunk
>
> Attachments: AMBARI-21001.patch
>
>
> 1. Create a Hive 1.5.0 view instance execute it in IE 11.
> 2. A blank page is displayed with the following error message in the web
> console:
> SCRIPT1002: Syntax error
> File: hive.js, Line: 8374, Column: 23
> This is because the ES6 arrow (=>) functions are not supported in IE
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk
[
https://issues.apache.org/jira/browse/AMBARI-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007641#comment-16007641
]
Masahiro Tanaka commented on AMBARI-20983:
--
Should we use JDK7? I thinks its support is already finished.
> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
> Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy) SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor SKIPPED
> [INFO] Ambari Metrics Grafana SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO]
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install
> node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn
> (install node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:170)
> at
>
[jira] [Comment Edited] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk
[
https://issues.apache.org/jira/browse/AMBARI-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007641#comment-16007641
]
Masahiro Tanaka edited comment on AMBARI-20983 at 5/12/17 5:02 AM:
---
Should we use JDK7? I think its support is already finished.
was (Author: masatana):
Should we use JDK7? I thinks its support is already finished.
> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
> Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy) SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor SKIPPED
> [INFO] Ambari Metrics Grafana SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO]
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install
> node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn
> (install node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at
>
[jira] [Commented] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007618#comment-16007618 ] Hudson commented on AMBARI-20990: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1525 (See [https://builds.apache.org/job/Ambari-branch-2.5/1525/]) AMBARI-20990 : writing query properly to hdfs file for handling unicode (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=57a6d15f6b1a140f062d15da75a6acaab1ccc77c]) * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/files/FileService.java > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007613#comment-16007613 ] Hudson commented on AMBARI-20990: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7462 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7462/]) AMBARI-20990 : writing query properly to hdfs file for handling unicode (nitiraj.rathore: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fffd07c75ba1af09b0ba3fec347bd7a6fff87807]) * (edit) contrib/views/hive-next/src/main/java/org/apache/ambari/view/hive2/resources/files/FileService.java > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007578#comment-16007578 ] Nitiraj Singh Rathore commented on AMBARI-20981: committed to branch-2.5 and trunk. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at >
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Affects Version/s: (was: 2.5.2) (was: 2.5.1) > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia >Assignee: Nitiraj Singh Rathore > Labels: views > Fix For: 2.5.1 > > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) >
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Resolution: Fixed Assignee: Nitiraj Singh Rathore Fix Version/s: 2.5.1 Status: Resolved (was: Patch Available) > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia >Assignee: Nitiraj Singh Rathore > Labels: views > Fix For: 2.5.1 > > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at
[jira] [Updated] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package
[ https://issues.apache.org/jira/browse/AMBARI-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14160: Description: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. was: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. > Ambari Slider View should pick up multiple versions of the same app package > --- > > Key: AMBARI-14160 > URL: https://issues.apache.org/jira/browse/AMBARI-14160 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > I was validating some fix for Slider hbase with Gour. > A new Slider hbase app package was built and moved to under: > /var/lib/ambari-server/resources/apps > We tried naming the new app package ending with -ted.zip -999.zip > After 'ambari-server restart', the new app package was not picked up by > Ambari. > Ambari Slider View should be able to accommodate more than one version of app > package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 5/12/17 3:16 AM:
--
Escaping the dollar sign automatically is the desirable solution .
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is the desirable solution.
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21001) Hive 1.5.0 view does not load in Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-21001: Fix Version/s: trunk Status: Patch Available (was: In Progress) > Hive 1.5.0 view does not load in Internet Explorer 11 > - > > Key: AMBARI-21001 > URL: https://issues.apache.org/jira/browse/AMBARI-21001 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk, 2.5.1 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-21001.patch > > > 1. Create a Hive 1.5.0 view instance execute it in IE 11. > 2. A blank page is displayed with the following error message in the web > console: > SCRIPT1002: Syntax error > File: hive.js, Line: 8374, Column: 23 > This is because the ES6 arrow (=>) functions are not supported in IE -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21001) Hive 1.5.0 view does not load in Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-21001: Attachment: AMBARI-21001.patch > Hive 1.5.0 view does not load in Internet Explorer 11 > - > > Key: AMBARI-21001 > URL: https://issues.apache.org/jira/browse/AMBARI-21001 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk, 2.5.1 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-21001.patch > > > 1. Create a Hive 1.5.0 view instance execute it in IE 11. > 2. A blank page is displayed with the following error message in the web > console: > SCRIPT1002: Syntax error > File: hive.js, Line: 8374, Column: 23 > This is because the ES6 arrow (=>) functions are not supported in IE -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21001) Hive 1.5.0 view does not load in Internet Explorer 11
Sangeeta Ravindran created AMBARI-21001: --- Summary: Hive 1.5.0 view does not load in Internet Explorer 11 Key: AMBARI-21001 URL: https://issues.apache.org/jira/browse/AMBARI-21001 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: trunk, 2.5.1 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran 1. Create a Hive 1.5.0 view instance execute it in IE 11. 2. A blank page is displayed with the following error message in the web console: SCRIPT1002: Syntax error File: hive.js, Line: 8374, Column: 23 This is because the ES6 arrow (=>) functions are not supported in IE -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007459#comment-16007459 ] Hudson commented on AMBARI-20999: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7461 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7461/]) AMBARI-20999. More updates to llap configs for hdp stack (Siddharth via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f7e9af87c75d8641a96b8b097b7b44f0a9f13538]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch, Screen Shot 2017-05-11 at 4.31.31 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20853) Service Advisor - Allow Service to define its Advisor Type as Python or Java
[ https://issues.apache.org/jira/browse/AMBARI-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20853: - Status: Patch Available (was: In Progress) > Service Advisor - Allow Service to define its Advisor Type as Python or Java > > > Key: AMBARI-20853 > URL: https://issues.apache.org/jira/browse/AMBARI-20853 > Project: Ambari > Issue Type: Story > Components: service-advisor >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20853.patch > > > See Epic AMBARI-20852 > First step is to allow a Service's metainfo.xml file to define what type of > Service Advisor it uses, Python or Java. > For now, continue to call Python for all services. > If set to Java, call a jar that ends up calling the existing Service Advisor > in Python as a way to ensure compatibility. > If set to Python, continue to call the current script. > In both cases, we will continue to generate the services.json file -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20853) Service Advisor - Allow Service to define its Advisor Type as Python or Java
[ https://issues.apache.org/jira/browse/AMBARI-20853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20853: - Attachment: AMBARI-20853.patch > Service Advisor - Allow Service to define its Advisor Type as Python or Java > > > Key: AMBARI-20853 > URL: https://issues.apache.org/jira/browse/AMBARI-20853 > Project: Ambari > Issue Type: Story > Components: service-advisor >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk > > Attachments: AMBARI-20853.patch > > > See Epic AMBARI-20852 > First step is to allow a Service's metainfo.xml file to define what type of > Service Advisor it uses, Python or Java. > For now, continue to call Python for all services. > If set to Java, call a jar that ends up calling the existing Service Advisor > in Python as a way to ensure compatibility. > If set to Python, continue to call the current script. > In both cases, we will continue to generate the services.json file -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007443#comment-16007443 ] Hudson commented on AMBARI-20999: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1524 (See [https://builds.apache.org/job/Ambari-branch-2.5/1524/]) AMBARI-20999. More updates to llap configs for hdp stack (Siddharth via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7f2f40e33dd66e49192efd46c6e7a11c31b3c643]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/hive-interactive-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/tez-interactive-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch, Screen Shot 2017-05-11 at 4.31.31 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007398#comment-16007398 ] Sumit Mohanty commented on AMBARI-20999: Will fix the unit tests and commit. > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch, Screen Shot 2017-05-11 at 4.31.31 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007397#comment-16007397 ] Hudson commented on AMBARI-20977: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7460 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7460/]) AMBARI-20977. Journalnode should support bulk restart o start or stop in (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=023c819a3d05c5bd8fbf1933930fbc5ddfda6e16]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metainfo.xml > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007373#comment-16007373 ] Swapan Shridhar commented on AMBARI-20999: -- This removal still has reference: [^Screen Shot 2017-05-11 at 4.31.31 PM.png]. Shouldn't re removed. > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch, Screen Shot 2017-05-11 at 4.31.31 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20999: - Attachment: Screen Shot 2017-05-11 at 4.31.31 PM.png > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch, Screen Shot 2017-05-11 at 4.31.31 > PM.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[
https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007362#comment-16007362
]
Sumit Mohanty commented on AMBARI-20999:
[~sseth] looks like there is an unit test failure
{code}
Running org.apache.ambari.server.upgrade.UpgradeCatalog250Test
Tests run: 24, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.848 sec <<<
FAILURE! - in org.apache.ambari.server.upgrade.UpgradeCatalog250Test
testUpdateHiveConfigs(org.apache.ambari.server.upgrade.UpgradeCatalog250Test)
Time elapsed: 0.01 sec <<< ERROR!
java.lang.NullPointerException
at
org.apache.ambari.server.upgrade.UpgradeCatalog250Test.testUpdateHiveConfigs(UpgradeCatalog250Test.java:1716)
Results :
Tests in error:
UpgradeCatalog250Test.testUpdateHiveConfigs:1716 » NullPointer
{code}
> More updates to llap configs for hdp stack
> --
>
> Key: AMBARI-20999
> URL: https://issues.apache.org/jira/browse/AMBARI-20999
> Project: Ambari
> Issue Type: Task
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20999.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value
[
https://issues.apache.org/jira/browse/AMBARI-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rogue Hosaka updated AMBARI-20220:
--
Thanks for the time you give me .. I'm new to HDP, I downloaded the virtual
machine on VMware Fusion. I am a computer security student, and I am French. I
try to set up KnoxSSO and when I restart the server with the command
"ambari-server restart" I encounter the famous error. So I did some research
that led me to you and your patch. I will try to update ambari-server.
Otherwise can you tell me what I need to change on the file
"ambari_server_main.py" or I have to apply the patch on it? Sorry for my
English…
> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty
> loads classes from views, the more views which are installed increases the
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check found warnings. See
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still
> valuable to have this startup property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007354#comment-16007354 ] Swapan Shridhar commented on AMBARI-20999: -- +1 for [^AMBARI-20999.01.patch] > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region
[ https://issues.apache.org/jira/browse/AMBARI-20977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-20977: - Resolution: Fixed Fix Version/s: (was: 2.5.1) Status: Resolved (was: Patch Available) Pushed to trunk, commit 023c819a3d05c5bd8fbf1933930fbc5ddfda6e16 > Journalnode should support batch restart in hosts' page likeing datanode or > region > -- > > Key: AMBARI-20977 > URL: https://issues.apache.org/jira/browse/AMBARI-20977 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: zhangxiaolu >Assignee: zhangxiaolu > Fix For: trunk > > Attachments: AMBARI-20977.patch > > > Journalnode should support batch restart in hosts' page likeing datanode or > region. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21000) Ambari does not work with PGBouncer/PostgreSQL
[ https://issues.apache.org/jira/browse/AMBARI-21000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Yokota updated AMBARI-21000: --- Status: Patch Available (was: Open) > Ambari does not work with PGBouncer/PostgreSQL > -- > > Key: AMBARI-21000 > URL: https://issues.apache.org/jira/browse/AMBARI-21000 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Robert Yokota > Attachments: AMBARI-21000.01.patch > > > When using JDBC with PGBouncer (a connection pooler for PostgreSQL), prepared > statements must be disabled on the client side. According to the PgBouncer > FAQ, this is done by passing "prepareThreshold=0" in the JDBC URL. Even when > using "prepareThreshold=0", Ambari returns errors of the form "prepared > statement "S_1" does not exist". This is because Ambari uses Quartz, which > uses C3P0. Quartz by default configures C3P0 to cache prepared statements by > setting maxStatementsPerConnection=120. Fortunately, Quartz also allows you > to override this C3P0 setting by passing a property named > "maxCachedStatementsPerConnection". When setting this property to 0 (which > is the default in C3P0), then Ambari works properly with PGBouncer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21000) Ambari does not work with PGBouncer/PostgreSQL
[ https://issues.apache.org/jira/browse/AMBARI-21000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Yokota updated AMBARI-21000: --- Attachment: AMBARI-21000.01.patch This patch exposes the Quartz setting as the Ambari setting "server.execution.scheduler.maxStatementsPerConnection", which can then be set to 0 when using PGBouncer > Ambari does not work with PGBouncer/PostgreSQL > -- > > Key: AMBARI-21000 > URL: https://issues.apache.org/jira/browse/AMBARI-21000 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Robert Yokota > Attachments: AMBARI-21000.01.patch > > > When using JDBC with PGBouncer (a connection pooler for PostgreSQL), prepared > statements must be disabled on the client side. According to the PgBouncer > FAQ, this is done by passing "prepareThreshold=0" in the JDBC URL. Even when > using "prepareThreshold=0", Ambari returns errors of the form "prepared > statement "S_1" does not exist". This is because Ambari uses Quartz, which > uses C3P0. Quartz by default configures C3P0 to cache prepared statements by > setting maxStatementsPerConnection=120. Fortunately, Quartz also allows you > to override this C3P0 setting by passing a property named > "maxCachedStatementsPerConnection". When setting this property to 0 (which > is the default in C3P0), then Ambari works properly with PGBouncer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21000) Ambari does not work with PGBouncer/PostgreSQL
Robert Yokota created AMBARI-21000: -- Summary: Ambari does not work with PGBouncer/PostgreSQL Key: AMBARI-21000 URL: https://issues.apache.org/jira/browse/AMBARI-21000 Project: Ambari Issue Type: Bug Affects Versions: 2.5.2 Reporter: Robert Yokota When using JDBC with PGBouncer (a connection pooler for PostgreSQL), prepared statements must be disabled on the client side. According to the PgBouncer FAQ, this is done by passing "prepareThreshold=0" in the JDBC URL. Even when using "prepareThreshold=0", Ambari returns errors of the form "prepared statement "S_1" does not exist". This is because Ambari uses Quartz, which uses C3P0. Quartz by default configures C3P0 to cache prepared statements by setting maxStatementsPerConnection=120. Fortunately, Quartz also allows you to override this C3P0 setting by passing a property named "maxCachedStatementsPerConnection". When setting this property to 0 (which is the default in C3P0), then Ambari works properly with PGBouncer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007281#comment-16007281 ] Sumit Mohanty commented on AMBARI-20999: LGTM, +1 > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20999: --- Priority: Blocker (was: Major) > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-20999: Attachment: AMBARI-20999.01.patch [~sumitmohanty], [~swapanshridhar] - could you please take a look. Patch adds/changes a bunch of configs. Also gets rid of unnecessary changes in UpgradeCatalog250. (There's still some setting there related to hs2heapsize. Not sure why though) > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20999) More updates to llap configs for hdp stack
[ https://issues.apache.org/jira/browse/AMBARI-20999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated AMBARI-20999: Status: Patch Available (was: Open) > More updates to llap configs for hdp stack > -- > > Key: AMBARI-20999 > URL: https://issues.apache.org/jira/browse/AMBARI-20999 > Project: Ambari > Issue Type: Task >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.1 > > Attachments: AMBARI-20999.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20999) More updates to llap configs for hdp stack
Siddharth Seth created AMBARI-20999: --- Summary: More updates to llap configs for hdp stack Key: AMBARI-20999 URL: https://issues.apache.org/jira/browse/AMBARI-20999 Project: Ambari Issue Type: Task Reporter: Siddharth Seth Assignee: Siddharth Seth Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20998) HDP 3.0 TP - create Service Advisor for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-20998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20998: --- Attachment: AMBARI-20998.patch > HDP 3.0 TP - create Service Advisor for Ranger > -- > > Key: AMBARI-20998 > URL: https://issues.apache.org/jira/browse/AMBARI-20998 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20998.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20998) HDP 3.0 TP - create Service Advisor for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-20998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20998: --- Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for Ranger > -- > > Key: AMBARI-20998 > URL: https://issues.apache.org/jira/browse/AMBARI-20998 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20998.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20998) HDP 3.0 TP - create Service Advisor for Ranger
Vitaly Brodetskyi created AMBARI-20998: -- Summary: HDP 3.0 TP - create Service Advisor for Ranger Key: AMBARI-20998 URL: https://issues.apache.org/jira/browse/AMBARI-20998 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20997) Ambari upgrade failed
[ https://issues.apache.org/jira/browse/AMBARI-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20997: - Status: Patch Available (was: In Progress) > Ambari upgrade failed > - > > Key: AMBARI-20997 > URL: https://issues.apache.org/jira/browse/AMBARI-20997 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20997.patch > > > java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword > org.apache.ambari.server.AmbariException: ORA-00971: missing SET keyword > Caused by: java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20997) Ambari upgrade failed
[ https://issues.apache.org/jira/browse/AMBARI-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-20997: - Attachment: AMBARI-20997.patch > Ambari upgrade failed > - > > Key: AMBARI-20997 > URL: https://issues.apache.org/jira/browse/AMBARI-20997 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20997.patch > > > java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword > org.apache.ambari.server.AmbariException: ORA-00971: missing SET keyword > Caused by: java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value
[
https://issues.apache.org/jira/browse/AMBARI-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007004#comment-16007004
]
Jonathan Hurley commented on AMBARI-20220:
--
I don't think you can attach screenshots here... But aside from the one file I
pointed out, the other file is a Java file which is build into the JAR, so you
wouldn't be able to replace it. Why are you trying to take this as a patch on
top of an install? If that's what you're doing then you only need to change
ambari_server_main.py until you can do an official ambari-server upgrade.
> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty
> loads classes from views, the more views which are installed increases the
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check found warnings. See
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still
> valuable to have this startup property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006964#comment-16006964 ] Tim Thorpe commented on AMBARI-20992: - The failing test is not related to my change: Test Result (1 failure / ±0) org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSinkTest.testMetricsRetrievalExceptionTolerance > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. This > affects the metainfo.xml from common-services/HDFS both 2.1.0.2.0 and > 3.0.0.3.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20996) Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors
[
https://issues.apache.org/jira/browse/AMBARI-20996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20996:
-
Attachment: AMBARI-20996.patch
> Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors
> -
>
> Key: AMBARI-20996
> URL: https://issues.apache.org/jira/browse/AMBARI-20996
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20996.patch
>
>
> Without a "current cluster version", the value being passed into python is
> currently {{None}}. This will be changed as we begin passing down service
> repository versions instead.
> However, in the meantime, there are upgrade failures when this value is empty
> since the fallback code is trying to use "HDP-2.5" and is not able to
> normalize this out to "2.5.0.0":
> {code}
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/params_linux.py",
> line 77, in
> stack_supports_ranger_kerberos =
> check_stack_feature(StackFeature.RANGER_KERBEROS_SUPPORT,
> version_for_stack_feature_checks)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_features.py",
> line 57, in check_stack_feature
> if compare_versions(stack_version, min_version, format = True) < 0:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
> line 77, in compare_versions
> return cmp(_normalize(v1, desired_segments=max_segments), _normalize(v2,
> desired_segments=max_segments))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
> line 34, in _normalize
> return [int(x) for x in v_list]
> ValueError: invalid literal for int() with base 10: ''
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20996) Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors
[
https://issues.apache.org/jira/browse/AMBARI-20996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20996:
-
Status: Patch Available (was: Open)
> Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors
> -
>
> Key: AMBARI-20996
> URL: https://issues.apache.org/jira/browse/AMBARI-20996
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20996.patch
>
>
> Without a "current cluster version", the value being passed into python is
> currently {{None}}. This will be changed as we begin passing down service
> repository versions instead.
> However, in the meantime, there are upgrade failures when this value is empty
> since the fallback code is trying to use "HDP-2.5" and is not able to
> normalize this out to "2.5.0.0":
> {code}
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/params_linux.py",
> line 77, in
> stack_supports_ranger_kerberos =
> check_stack_feature(StackFeature.RANGER_KERBEROS_SUPPORT,
> version_for_stack_feature_checks)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_features.py",
> line 57, in check_stack_feature
> if compare_versions(stack_version, min_version, format = True) < 0:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
> line 77, in compare_versions
> return cmp(_normalize(v1, desired_segments=max_segments), _normalize(v2,
> desired_segments=max_segments))
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
> line 34, in _normalize
> return [int(x) for x in v_list]
> ValueError: invalid literal for int() with base 10: ''
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[
https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006917#comment-16006917
]
Hadoop QA commented on AMBARI-20698:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12866984/AMBARI-20698.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11583//console
This message is automatically generated.
> Ability to export blueprint via Ambari installer UI
> ---
>
> Key: AMBARI-20698
> URL: https://issues.apache.org/jira/browse/AMBARI-20698
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20698.patch, Generate blueprint via Ambari
> Installer UI - v2.pdf
>
>
> UI be able to export a blueprint when a user reaches the Deploy page and the
> bp can be used to install a cluster later on.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006918#comment-16006918 ] Hudson commented on AMBARI-20992: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7459 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7459/]) AMBARI-20992 - HDFS metainfo.xml has the wrong scope for component (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1d46f23f743bf64a3d086863af02d15aeb36f484]) * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metainfo.xml > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. This > affects the metainfo.xml from common-services/HDFS both 2.1.0.2.0 and > 3.0.0.3.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20997) Ambari upgrade failed
Dmytro Grinenko created AMBARI-20997: Summary: Ambari upgrade failed Key: AMBARI-20997 URL: https://issues.apache.org/jira/browse/AMBARI-20997 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.1 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Priority: Critical Fix For: 2.5.1 java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword org.apache.ambari.server.AmbariException: ORA-00971: missing SET keyword Caused by: java.sql.SQLSyntaxErrorException: ORA-00971: missing SET keyword -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk > > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. This > affects the metainfo.xml from common-services/HDFS both 2.1.0.2.0 and > 3.0.0.3.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20996) Fallback Cluster Current Version Is Blank Which Causes Upgrade Errors
Jonathan Hurley created AMBARI-20996:
Summary: Fallback Cluster Current Version Is Blank Which Causes
Upgrade Errors
Key: AMBARI-20996
URL: https://issues.apache.org/jira/browse/AMBARI-20996
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: trunk
Without a "current cluster version", the value being passed into python is
currently {{None}}. This will be changed as we begin passing down service
repository versions instead.
However, in the meantime, there are upgrade failures when this value is empty
since the fallback code is trying to use "HDP-2.5" and is not able to normalize
this out to "2.5.0.0":
{code}
File
"/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/params_linux.py",
line 77, in
stack_supports_ranger_kerberos =
check_stack_feature(StackFeature.RANGER_KERBEROS_SUPPORT,
version_for_stack_feature_checks)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/stack_features.py",
line 57, in check_stack_feature
if compare_versions(stack_version, min_version, format = True) < 0:
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
line 77, in compare_versions
return cmp(_normalize(v1, desired_segments=max_segments), _normalize(v2,
desired_segments=max_segments))
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/version.py",
line 34, in _normalize
return [int(x) for x in v_list]
ValueError: invalid literal for int() with base 10: ''
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20995) Integrate ServiceService resource and it's subresources with swagger
Balázs Bence Sári created AMBARI-20995: -- Summary: Integrate ServiceService resource and it's subresources with swagger Key: AMBARI-20995 URL: https://issues.apache.org/jira/browse/AMBARI-20995 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20994) Integrate RootServiceService with Swagger
[ https://issues.apache.org/jira/browse/AMBARI-20994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-20994: --- Attachment: AMBARI-20994.patch > Integrate RootServiceService with Swagger > - > > Key: AMBARI-20994 > URL: https://issues.apache.org/jira/browse/AMBARI-20994 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-20994.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20994) Integrate RootServiceService with Swagger
Doroszlai, Attila created AMBARI-20994: -- Summary: Integrate RootServiceService with Swagger Key: AMBARI-20994 URL: https://issues.apache.org/jira/browse/AMBARI-20994 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Doroszlai, Attila Assignee: Doroszlai, Attila Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20993) Stack advisor needs to enforce conditional component dependency for slaves and masters
Tim Thorpe created AMBARI-20993: --- Summary: Stack advisor needs to enforce conditional component dependency for slaves and masters Key: AMBARI-20993 URL: https://issues.apache.org/jira/browse/AMBARI-20993 Project: Ambari Issue Type: New Feature Components: ambari-server Affects Versions: trunk Reporter: Tim Thorpe Assignee: Tim Thorpe AMBARI-19685 started the work but is only enforcing non-conditional dependencies for slaves and masters. This will add in the ability to validate the layout and the configuration for conditional dependencies both for "property exists" and "property equals" type of dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Description: HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are listed with host. They should all have cluster scope. This affects the metainfo.xml from common-services/HDFS both 2.1.0.2.0 and 3.0.0.3.0. (was: HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are listed with host. They should all have cluster scope.) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. This > affects the metainfo.xml from common-services/HDFS both 2.1.0.2.0 and > 3.0.0.3.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Attachment: AMBARI-20992.patch > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Status: Patch Available (was: Open) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Status: Open (was: Patch Available) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Attachment: (was: AMBARI-20992.patch) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Attachment: AMBARI-20992.patch > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20992: Status: Patch Available (was: Open) > HDFS metainfo.xml has the wrong scope for component dependencies > > > Key: AMBARI-20992 > URL: https://issues.apache.org/jira/browse/AMBARI-20992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-20992.patch > > > HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are > listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20992) HDFS metainfo.xml has the wrong scope for component dependencies
Tim Thorpe created AMBARI-20992: --- Summary: HDFS metainfo.xml has the wrong scope for component dependencies Key: AMBARI-20992 URL: https://issues.apache.org/jira/browse/AMBARI-20992 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Tim Thorpe Assignee: Tim Thorpe HDFS/ZKFC, ZOOKEEPER/ZOOKEEPER_SERVER and HDFS/JOURNALNODE all currently are listed with host. They should all have cluster scope. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20991) Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
[
https://issues.apache.org/jira/browse/AMBARI-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20991:
-
Attachment: AMBARI-20991.patch
> Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
>
>
> Key: AMBARI-20991
> URL: https://issues.apache.org/jira/browse/AMBARI-20991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-20991.patch
>
>
> The cluster version state is not taking into account the correct values for
> {{SERVICE}} and {{PATCH}} upgrades. When at least host is {{NOT_REQUIRED}},
> the aggregate value is marked as {{INSTALLING}}.
> {code}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/stack_versions/2;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 2,
> "repository_version": 2,
> "stack": "HDP",
> "state": "INSTALLING",
> "version": "2.5",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [
> "c6401.ambari.apache.org"
> ],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> "NOT_REQUIRED": [
> "c6402.ambari.apache.org",
> "c6403.ambari.apache.org"
> ],
> "OUT_OF_SYNC": []
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20991) Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
[
https://issues.apache.org/jira/browse/AMBARI-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20991:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
>
>
> Key: AMBARI-20991
> URL: https://issues.apache.org/jira/browse/AMBARI-20991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-20991.patch
>
>
> The cluster version state is not taking into account the correct values for
> {{SERVICE}} and {{PATCH}} upgrades. When at least host is {{NOT_REQUIRED}},
> the aggregate value is marked as {{INSTALLING}}.
> {code}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/stack_versions/2;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 2,
> "repository_version": 2,
> "stack": "HDP",
> "state": "INSTALLING",
> "version": "2.5",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [
> "c6401.ambari.apache.org"
> ],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> "NOT_REQUIRED": [
> "c6402.ambari.apache.org",
> "c6403.ambari.apache.org"
> ],
> "OUT_OF_SYNC": []
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20991) Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
[
https://issues.apache.org/jira/browse/AMBARI-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20991:
-
Status: Patch Available (was: Open)
> Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
>
>
> Key: AMBARI-20991
> URL: https://issues.apache.org/jira/browse/AMBARI-20991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-20991.patch
>
>
> The cluster version state is not taking into account the correct values for
> {{SERVICE}} and {{PATCH}} upgrades. When at least host is {{NOT_REQUIRED}},
> the aggregate value is marked as {{INSTALLING}}.
> {code}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/stack_versions/2;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 2,
> "repository_version": 2,
> "stack": "HDP",
> "state": "INSTALLING",
> "version": "2.5",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [
> "c6401.ambari.apache.org"
> ],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> "NOT_REQUIRED": [
> "c6402.ambari.apache.org",
> "c6403.ambari.apache.org"
> ],
> "OUT_OF_SYNC": []
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20991) Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
[
https://issues.apache.org/jira/browse/AMBARI-20991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20991:
-
Summary: Cluster Repository State Is Not Calculated Correctly For
Service/Patch Repos (was: Fix Calculation of Cluster Repository State)
> Cluster Repository State Is Not Calculated Correctly For Service/Patch Repos
>
>
> Key: AMBARI-20991
> URL: https://issues.apache.org/jira/browse/AMBARI-20991
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
>
> The cluster version state is not taking into account the correct values for
> {{SERVICE}} and {{PATCH}} upgrades. When at least host is {{NOT_REQUIRED}},
> the aggregate value is marked as {{INSTALLING}}.
> {code}
> {
> "href": "http://localhost:8080/api/v1/clusters/c1/stack_versions/2;,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 2,
> "repository_version": 2,
> "stack": "HDP",
> "state": "INSTALLING",
> "version": "2.5",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [
> "c6401.ambari.apache.org"
> ],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> "NOT_REQUIRED": [
> "c6402.ambari.apache.org",
> "c6403.ambari.apache.org"
> ],
> "OUT_OF_SYNC": []
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20991) Fix Calculation of Cluster Repository State
Jonathan Hurley created AMBARI-20991:
Summary: Fix Calculation of Cluster Repository State
Key: AMBARI-20991
URL: https://issues.apache.org/jira/browse/AMBARI-20991
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: trunk
The cluster version state is not taking into account the correct values for
{{SERVICE}} and {{PATCH}} upgrades. When at least host is {{NOT_REQUIRED}}, the
aggregate value is marked as {{INSTALLING}}.
{code}
{
"href": "http://localhost:8080/api/v1/clusters/c1/stack_versions/2;,
"ClusterStackVersions": {
"cluster_name": "c1",
"id": 2,
"repository_version": 2,
"stack": "HDP",
"state": "INSTALLING",
"version": "2.5",
"host_states": {
"CURRENT": [],
"INIT": [],
"INSTALLED": [
"c6401.ambari.apache.org"
],
"INSTALLING": [],
"INSTALL_FAILED": [],
"NOT_REQUIRED": [
"c6402.ambari.apache.org",
"c6403.ambari.apache.org"
],
"OUT_OF_SYNC": []
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed
[
https://issues.apache.org/jira/browse/AMBARI-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006624#comment-16006624
]
Hudson commented on AMBARI-20980:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7458 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7458/])
AMBARI-20980. RU: RESTART SPARK2/SPARK2_CLIENT failed (dlysnichenko)
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e2dd63b7a3b7509a28b12641de87122eda0e33e])
* (edit)
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK/2.2.0/package/scripts/params.py
> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 60, in
> SparkClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 315, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 51, in pre_upgrade_restart
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
> line 209, in
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present
> even if livy2 is not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed
[
https://issues.apache.org/jira/browse/AMBARI-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006534#comment-16006534
]
Hudson commented on AMBARI-20980:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1523 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1523/])
AMBARI-20980. RU: RESTART SPARK2/SPARK2_CLIENT failed (dlysnichenko)
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ef6c72da3ef1a9441ec8f374528ebad74a6e1f32])
* (edit)
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 60, in
> SparkClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 315, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 51, in pre_upgrade_restart
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
> line 209, in
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present
> even if livy2 is not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20988) Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL
[ https://issues.apache.org/jira/browse/AMBARI-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006531#comment-16006531 ] Hudson commented on AMBARI-20988: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1523 (See [https://builds.apache.org/job/Ambari-branch-2.5/1523/]) AMBARI-20988. Add missing 'cluster_host_info' column to 'request' table (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4aff24a915de9feed690769bbf8dab2bbb171d42]) * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql > Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL > -- > > Key: AMBARI-20988 > URL: https://issues.apache.org/jira/browse/AMBARI-20988 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.1 > > Attachments: AMBARI-20988.b25.v1.patch > > > https://issues.apache.org/jira/browse/AMBARI-20919 moved the > cluster_host_info column from stage table into request table. The change > missed to cover the Ambari database schema DDL for MS SQL server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed
[
https://issues.apache.org/jira/browse/AMBARI-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-20980:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
4aff24a915..ef6c72da3e branch-2.5 -> branch-2.5
3edbc2c41d..7e2dd63b7a trunk -> trunk
> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 60, in
> SparkClient().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 315, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
> line 51, in pre_upgrade_restart
> import params
> File
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
> line 209, in
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present
> even if livy2 is not installed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20984) Be able to include HDP repos in blueprint
[
https://issues.apache.org/jira/browse/AMBARI-20984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006489#comment-16006489
]
Hadoop QA commented on AMBARI-20984:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12867435/AMBARI-20984.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.topology.ClusterInstallWithoutStartTest
org.apache.ambari.server.topology.ClusterDeployWithStartOnlyTest
org.apache.ambari.server.state.UpgradeHelperTest
org.apache.ambari.server.topology.TopologyManagerTest
org.apache.ambari.server.topology.ClusterInstallWithoutStartOnComponentLevelTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11582//console
This message is automatically generated.
> Be able to include HDP repos in blueprint
> -
>
> Key: AMBARI-20984
> URL: https://issues.apache.org/jira/browse/AMBARI-20984
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: ambari-server
>
> Attachments: AMBARI-20984.patch
>
>
> Currently, if a user wants to use custom HDP repos during a blueprint
> deployment, he has to update the repo URLs before hand via a REST API. The
> JIRA here proposes a way to include stack repos in the blueprint as optional
> fields so that when the fields exist, Ambari server will use the repos to
> deploy a cluster. This eliminates the need for user to run a separate rest
> api call before the actual blueprint deployment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value
[
https://issues.apache.org/jira/browse/AMBARI-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rogue Hosaka updated AMBARI-20220:
--
Hello,
Can you give me the links of all the file to patch? I sent you a screenshot to
show you where I am stuck.
> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty
> loads classes from views, the more views which are installed increases the
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check found warnings. See
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still
> valuable to have this startup property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Status: Patch Available (was: Open) > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Attachment: AMBARI-20990_branch-2.5.patch > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20990_branch-2.5.patch > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
[ https://issues.apache.org/jira/browse/AMBARI-20990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20990: --- Description: Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Refresh page. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. was: Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. > Hive view 1.5 : Saved query garbles the unicode characters in query. > > > Key: AMBARI-20990 > URL: https://issues.apache.org/jira/browse/AMBARI-20990 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > > Steps to reproduce. > 1. Open query editor of hive view 1.5. > 2. Enter a simple query with unicode character like > select '昔々' > 3. click on "save as" button. Save the query. > 4. Refresh page. Go to the saved queries tab and click open the saved query. > 5. in the query editor you will not see the unicode characters you entered. > Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20988) Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL
[ https://issues.apache.org/jira/browse/AMBARI-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-20988: -- Attachment: AMBARI-20988.b25.v1.patch > Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL > -- > > Key: AMBARI-20988 > URL: https://issues.apache.org/jira/browse/AMBARI-20988 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.1 > > Attachments: AMBARI-20988.b25.v1.patch > > > https://issues.apache.org/jira/browse/AMBARI-20919 moved the > cluster_host_info column from stage table into request table. The change > missed to cover the Ambari database schema DDL for MS SQL server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20988) Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL
[ https://issues.apache.org/jira/browse/AMBARI-20988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-20988: -- Status: Patch Available (was: In Progress) > Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL > -- > > Key: AMBARI-20988 > URL: https://issues.apache.org/jira/browse/AMBARI-20988 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sebastian Toader > Fix For: 2.5.1 > > Attachments: AMBARI-20988.b25.v1.patch > > > https://issues.apache.org/jira/browse/AMBARI-20919 moved the > cluster_host_info column from stage table into request table. The change > missed to cover the Ambari database schema DDL for MS SQL server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20990) Hive view 1.5 : Saved query garbles the unicode characters in query.
Nitiraj Singh Rathore created AMBARI-20990: -- Summary: Hive view 1.5 : Saved query garbles the unicode characters in query. Key: AMBARI-20990 URL: https://issues.apache.org/jira/browse/AMBARI-20990 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.2 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.5.1 Steps to reproduce. 1. Open query editor of hive view 1.5. 2. Enter a simple query with unicode character like > select '昔々' 3. click on "save as" button. Save the query. 4. Go to the saved queries tab and click open the saved query. 5. in the query editor you will not see the unicode characters you entered. Instead you will see some garbled characters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20989) Ambari infra manager: add batch support
[ https://issues.apache.org/jira/browse/AMBARI-20989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20989: -- Status: Patch Available (was: Open) > Ambari infra manager: add batch support > --- > > Key: AMBARI-20989 > URL: https://issues.apache.org/jira/browse/AMBARI-20989 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-20989.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20989) Ambari infra manager: add batch support
[ https://issues.apache.org/jira/browse/AMBARI-20989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20989: -- Attachment: AMBARI-20989.patch > Ambari infra manager: add batch support > --- > > Key: AMBARI-20989 > URL: https://issues.apache.org/jira/browse/AMBARI-20989 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.5.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-20989.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20872) Defer validation of required configuration from the blueprint validator to a point where all the configuration is available.
[ https://issues.apache.org/jira/browse/AMBARI-20872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006377#comment-16006377 ] Hudson commented on AMBARI-20872: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7457 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7457/]) AMBARI-20872 Required properties for services in the blueprint are (lpuskas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3edbc2c41d489c20d1f503723491461eaa328fab]) * (add) ambari-server/src/main/java/org/apache/ambari/server/topology/validators/RequiredConfigPropertiesValidator.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintValidatorImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/validators/TopologyValidatorFactory.java * (add) ambari-server/src/test/java/org/apache/ambari/server/topology/validators/RequiredConfigPropertiesValidatorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/BlueprintImplTest.java > Defer validation of required configuration from the blueprint validator to a > point where all the configuration is available. > > > Key: AMBARI-20872 > URL: https://issues.apache.org/jira/browse/AMBARI-20872 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Laszlo Puskas >Assignee: Laszlo Puskas > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-20872.trunk.v1.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > Validating whether all the required configuration properties are provided is > done when the blueprint is posted, however these properties can also be > provided in the cluster creation template. > This validation should be done later, when configuration from both the > blueprint and the cluster creation template is available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20989) Ambari infra manager: add batch support
Olivér Szabó created AMBARI-20989: - Summary: Ambari infra manager: add batch support Key: AMBARI-20989 URL: https://issues.apache.org/jira/browse/AMBARI-20989 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.5.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006320#comment-16006320 ] Hudson commented on AMBARI-20978: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7456 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7456/]) AMBARI-20978 Ambari 3.0: Outstanding new components issues, additional (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=55750b92a4f7ad00d2a63211f8b34364b47df289]) * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css * (edit) ambari-web/app/styles/wizard.less > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value
[
https://issues.apache.org/jira/browse/AMBARI-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006319#comment-16006319
]
Jonathan Hurley commented on AMBARI-20220:
--
You can find {{ambari_server_main.py}} in {{/usr/sbin/ambari_server_main.py}}
> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty
> loads classes from views, the more views which are installed increases the
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check found warnings. See
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still
> valuable to have this startup property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20988) Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL
Sebastian Toader created AMBARI-20988: - Summary: Add missing 'cluster_host_info' column to 'request' table to MSSQL DDL Key: AMBARI-20988 URL: https://issues.apache.org/jira/browse/AMBARI-20988 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Sebastian Toader Assignee: Sebastian Toader Fix For: 2.5.1 https://issues.apache.org/jira/browse/AMBARI-20919 moved the cluster_host_info column from stage table into request table. The change missed to cover the Ambari database schema DDL for MS SQL server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20978: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006269#comment-16006269 ] Andrii Tkach commented on AMBARI-20978: --- additional patch committed to trunk > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006266#comment-16006266 ] Aleksandr Kovalenko commented on AMBARI-20978: -- +1 for second patch > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006256#comment-16006256 ] Hudson commented on AMBARI-20434: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7455 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7455/]) AMBARI-20434. Enhance Kafka Service Check. Additional changes (WangJie (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4b3cbef39edb37b8b393dd5b19c968223a282281]) * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka-broker.xml * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/service_check.py > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-20434-1.patch, AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[
https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006252#comment-16006252
]
Hadoop QA commented on AMBARI-20978:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12867545/AMBARI-20978_2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11581//console
This message is automatically generated.
> Ambari 3.0: Outstanding new components issues
> -
>
> Key: AMBARI-20978
> URL: https://issues.apache.org/jira/browse/AMBARI-20978
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3.
> disabled area too dark .png, 3. step2 disabled too dark and eye catching.png,
> 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch,
> AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png
>
>
> The following issues are related new style guide components:
> * Checkbox: some checkboxes are not centered. see attached (effected places:
> installer step 1, create widget step 3, and user settings do not show
> background ops checkbox)
> * Input: disabled area is too prominent, too dark. see attached.
> * Modal: some modal primary button has a blk border, should remove that.
> * Dropdown: on hovering each option, the background should be dark and text
> should be white.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20978: -- Status: Patch Available (was: Reopened) > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20978: -- Attachment: AMBARI-20978_2.patch > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978_2.patch, > AMBARI-20978.patch, Disabled fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20978) Ambari 3.0: Outstanding new components issues
[ https://issues.apache.org/jira/browse/AMBARI-20978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach reopened AMBARI-20978: --- > Ambari 3.0: Outstanding new components issues > - > > Key: AMBARI-20978 > URL: https://issues.apache.org/jira/browse/AMBARI-20978 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. > disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, > 4. modal button border.png, 4. modal button.png, AMBARI-20978.patch, Disabled > fields.png, dropdown select color 1.png > > > The following issues are related new style guide components: > * Checkbox: some checkboxes are not centered. see attached (effected places: > installer step 1, create widget step 3, and user settings do not show > background ops checkbox) > * Input: disabled area is too prominent, too dark. see attached. > * Modal: some modal primary button has a blk border, should remove that. > * Dropdown: on hovering each option, the background should be dark and text > should be white. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006212#comment-16006212 ] Dmitry Lysnichenko commented on AMBARI-20434: - Committed remote: ambari git commit: AMBARI-20434. Enhance Kafka Service Check. Additional changes (WangJie via dlysnichenko) To https://git-wip-us.apache.org/repos/asf/ambari.git 242d9e76f9..4b3cbef39e trunk -> trunk > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-20434-1.patch, AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20987) Hive View: does not show table properties via either describe or show create table
Hari Sekhon created AMBARI-20987: Summary: Hive View: does not show table properties via either describe or show create table Key: AMBARI-20987 URL: https://issues.apache.org/jira/browse/AMBARI-20987 Project: Ambari Issue Type: Bug Environment: HDP 2.5.0 + Hive View 1.5.0 Reporter: Hari Sekhon Ambari Hive View is not displaying the table properties that one normally sees on the command line when issuing "describe formatted" and "show create table" queries. It is only outputting the column list in the Result tab and does not appear to give another mechanism to investigate the table configurations. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20986) Remove redundant ajax url
[ https://issues.apache.org/jira/browse/AMBARI-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-20986: - Attachment: AMBARI-20986.patch > Remove redundant ajax url > - > > Key: AMBARI-20986 > URL: https://issues.apache.org/jira/browse/AMBARI-20986 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: wangjianfei >Assignee: wangjianfei > Fix For: trunk > > Attachments: AMBARI-20986.patch > > > Since we don't allow the user to turn on|off maintenance mode for individual > host components in AMBARI-5082,then the > bulk_request.hosts.all_components.passive_state ajax-sender url becomes > redundant.We should remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20986) Remove redundant ajax url
[ https://issues.apache.org/jira/browse/AMBARI-20986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-20986: - Status: Patch Available (was: Open) > Remove redundant ajax url > - > > Key: AMBARI-20986 > URL: https://issues.apache.org/jira/browse/AMBARI-20986 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: wangjianfei >Assignee: wangjianfei > Fix For: trunk > > Attachments: AMBARI-20986.patch > > > Since we don't allow the user to turn on|off maintenance mode for individual > host components in AMBARI-5082,then the > bulk_request.hosts.all_components.passive_state ajax-sender url becomes > redundant.We should remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20986) Remove redundant ajax url
wangjianfei created AMBARI-20986: Summary: Remove redundant ajax url Key: AMBARI-20986 URL: https://issues.apache.org/jira/browse/AMBARI-20986 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: trunk Reporter: wangjianfei Assignee: wangjianfei Fix For: trunk Since we don't allow the user to turn on|off maintenance mode for individual host components in AMBARI-5082,then the bulk_request.hosts.all_components.passive_state ajax-sender url becomes redundant.We should remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006073#comment-16006073 ] Nitiraj Singh Rathore edited comment on AMBARI-20981 at 5/11/17 8:31 AM: - [~gss2002] : Thanks for the patch. Although, your patch seems to be made by git only, but I was having problems in applying to the branch. So I did the same changes and created a new patch. attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. was (Author: nitiraj.rathore): attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at >
[jira] [Comment Edited] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16006073#comment-16006073 ] Nitiraj Singh Rathore edited comment on AMBARI-20981 at 5/11/17 8:25 AM: - attached AMBARI-20981_branch-2.5.patch : new patch with formatting and message. was (Author: nitiraj.rathore): attached AMBARI-20962_branch-2.5.patch : new patch with formatting and message. > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at >
[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long
[ https://issues.apache.org/jira/browse/AMBARI-20981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20981: --- Attachment: AMBARI-20981_branch-2.5.patch > Hive 2.0 View Table Statistics overflows Integer Type convert to Long > - > > Key: AMBARI-20981 > URL: https://issues.apache.org/jira/browse/AMBARI-20981 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.5.0, 2.5.1, 2.5.2 > Environment: Ambari 2.5.0.x >Reporter: Greg Senia > Labels: views > Attachments: AMBARI-20981_branch-2.5.patch, AMBARI-20981.patch > > > When testing with our extremely large datasets the statistics data returns a > failure and the following stack trace. Using Integer for Hive Table Stats > unfortunately is not going to work. It needs to be a long. I've provided a > patch to fix this. > 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] > ContainerResponse:419 - The RuntimeException could not be mapped to a > response, re-throwing to the HT > TP container > java.lang.NumberFormatException: For input string: "12375183159" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:583) > at java.lang.Integer.valueOf(Integer.java:766) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115) > at > org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62) > at > org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157) > at > org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278) > at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) >
