[jira] [Commented] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885308#comment-15885308 ] Doroszlai, Attila commented on AMBARI-20200: [~prabhjyotsingh], please make sure to create a separate patch including unit test change for trunk. > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch, AMBARI-20200_branch-2.5_v3.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20142) Job Link URL not working
[ https://issues.apache.org/jira/browse/AMBARI-20142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885294#comment-15885294 ] Hudson commented on AMBARI-20142: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1106 (See [https://builds.apache.org/job/Ambari-branch-2.5/1106/]) AMBARI-20142. Job Link URL not working.(Madhan Mohan Reddy via gauravn7) (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=259768314fbb6829623d096a632a919e94e29566]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-job-details.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-action.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/app/components/workflow-job-action.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/utils/common-utils.js * (add) contrib/views/wfmanager/src/main/resources/ui/tests/integration/components/workflow-job-action-test.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/workflow-job-details.hbs > Job Link URL not working > > > Key: AMBARI-20142 > URL: https://issues.apache.org/jira/browse/AMBARI-20142 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-20142_trunk.patch > > > Please give details and possible attach screen shots to clearly show what > went wrong. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20202) Show complete trace when server issue happens in WFM.
[ https://issues.apache.org/jira/browse/AMBARI-20202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB resolved AMBARI-20202. -- Resolution: Fixed > Show complete trace when server issue happens in WFM. > - > > Key: AMBARI-20202 > URL: https://issues.apache.org/jira/browse/AMBARI-20202 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Belliraj HB >Assignee: Belliraj HB > Labels: WFM > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20202) Show complete trace when server issue happens in WFM.
Belliraj HB created AMBARI-20202: Summary: Show complete trace when server issue happens in WFM. Key: AMBARI-20202 URL: https://issues.apache.org/jira/browse/AMBARI-20202 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Belliraj HB Assignee: Belliraj HB Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20128) Invalid error message while importing asset
[ https://issues.apache.org/jira/browse/AMBARI-20128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB resolved AMBARI-20128. -- Resolution: Fixed > Invalid error message while importing asset > --- > > Key: AMBARI-20128 > URL: https://issues.apache.org/jira/browse/AMBARI-20128 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > > Invalid error message is shown while importing asset. Its happening when user > tries to import asset from hdfs as well as from the DB. > Steps to reproduce : > 1) Publish an asset . > 2) Now try to import the asset. > 3) Once import is completed, open the settings for that particular action > node. Invalid Error message "Action contains elements that are not currently > supported by the designer." > Since the asset is as per workflow manager specification, this error message > should not be shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20129) Improper action node name after importing the asset
[ https://issues.apache.org/jira/browse/AMBARI-20129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB resolved AMBARI-20129. -- Resolution: Fixed > Improper action node name after importing the asset > > > Key: AMBARI-20129 > URL: https://issues.apache.org/jira/browse/AMBARI-20129 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma > Labels: WFD, WFM > Fix For: 2.5.0 > > > Action node name is not proper after importing asset. Once user imports the > asset, the node name is displayed as _undefined. > Instead of this, if there are no other action nodes of this type, then just > show the actual node name. > And if there are already existing nodes of this type, then show > _. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20130) UI is hung after clicking on error message link
[ https://issues.apache.org/jira/browse/AMBARI-20130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB resolved AMBARI-20130. -- Resolution: Fixed > UI is hung after clicking on error message link > --- > > Key: AMBARI-20130 > URL: https://issues.apache.org/jira/browse/AMBARI-20130 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > > UI is hung after clicking on error message link. > Steps to reproduce : > 1) Publish an asset . > 2) Now try to import the asset. > 3) Once import is completed, open the settings for that particular action > node. Invalid Error message "Action contains elements that are not currently > supported by the designer." > Once user clicks on this link, browser gets refreshed and its hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884982#comment-15884982
]
Hadoop QA commented on AMBARI-20197:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854790/AMBARI-20197.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10762//console
This message is automatically generated.
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884981#comment-15884981 ] Hudson commented on AMBARI-20201: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6866 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6866/]) AMBARI-20201. Config Groups are shown twice after creation (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2fc354e5cb0606622b869317ac98babc13d91fd4]) * (edit) ambari-web/app/controllers/main/service/manage_config_groups_controller.js > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * This added hosts. Hit OK. Hit Save. This brings you out of the config > group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884980#comment-15884980 ] Hudson commented on AMBARI-20201: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1105 (See [https://builds.apache.org/job/Ambari-branch-2.5/1105/]) AMBARI-20201. Config Groups are shown twice after creation (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5f0d00a6c8aa3055b202d1028deb24b484aebb03]) * (edit) ambari-web/app/controllers/main/service/manage_config_groups_controller.js > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * This added hosts. Hit OK. Hit Save. This brings you out of the config > group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Description: The same config group is being shown twice after config group creation. Here's what I did: * Go to Services > HDFS > Configs * Click on "Manage Config Groups" * There were two groups already (Default and AMS-DN) * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 * Clicked on hdfs-01 from the left panel * Clicked on the + icon from the right panel * This added hosts. Hit OK. Hit Save. This brings you out of the config group popups. * Back on the Service page, the click on "Manage Config Groups". There's a duplicate entry for hdfs-01 * Click on the config group pulldown. There's a duplicate entry for hdfs-01 - see config_group_pulldown.png * The duplicates go away after a page refresh was: The same config group is being shown twice after config group creation. Here's what I did: * Go to Services > HDFS > Configs * Click on "Manage Config Groups" * There were two groups already (Default and AMS-DN) * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 * Clicked on hdfs-01 from the left panel * Clicked on the + icon from the right panel * Used the filter to set "perf-c-1" * This added 111 hosts. Hit OK. Hit Save. This brings you out of the config group popups. * Back on the Service page, the click on "Manage Config Groups". There's a duplicate entry for hdfs-01 * Click on the config group pulldown. There's a duplicate entry for hdfs-01 - see config_group_pulldown.png * The duplicates go away after a page refresh > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * This added hosts. Hit OK. Hit Save. This brings you out of the config > group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Resolution: Fixed Status: Resolved (was: Patch Available) > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884974#comment-15884974 ] Aleksandr Kovalenko commented on AMBARI-20201: -- committed to trunk and branch-2.5 > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884973#comment-15884973 ] Aleksandr Kovalenko commented on AMBARI-20201: -- logic was not changed, no need to change unit tests > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20201) Config Groups are shown twice after creation
[
https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884972#comment-15884972
]
Hadoop QA commented on AMBARI-20201:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854795/AMBARI-20201.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10761//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10761//console
This message is automatically generated.
> Config Groups are shown twice after creation
>
>
> Key: AMBARI-20201
> URL: https://issues.apache.org/jira/browse/AMBARI-20201
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch,
> config_group_pulldown.png
>
>
> The same config group is being shown twice after config group creation.
> Here's what I did:
> * Go to Services > HDFS > Configs
> * Click on "Manage Config Groups"
> * There were two groups already (Default and AMS-DN)
> * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10
> * Clicked on hdfs-01 from the left panel
> * Clicked on the + icon from the right panel
> * Used the filter to set "perf-c-1"
> * This added 111 hosts. Hit OK. Hit Save. This brings you out of the
> config group popups.
> * Back on the Service page, the click on "Manage Config Groups". There's a
> duplicate entry for hdfs-01
> * Click on the config group pulldown. There's a duplicate entry for hdfs-01
> - see config_group_pulldown.png
> * The duplicates go away after a page refresh
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Attachment: AMBARI-20201.patch > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Attachment: AMBARI-20201_branch-2.5.patch > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Status: Patch Available (was: Open) > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20201_branch-2.5.patch, AMBARI-20201.patch, > config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20201) Config Groups are shown twice after creation
Aleksandr Kovalenko created AMBARI-20201: Summary: Config Groups are shown twice after creation Key: AMBARI-20201 URL: https://issues.apache.org/jira/browse/AMBARI-20201 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.5.0 Attachments: config_group_pulldown.png The same config group is being shown twice after config group creation. Here's what I did: * Go to Services > HDFS > Configs * Click on "Manage Config Groups" * There were two groups already (Default and AMS-DN) * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 * Clicked on hdfs-01 from the left panel * Clicked on the + icon from the right panel * Used the filter to set "perf-c-1" * This added 111 hosts. Hit OK. Hit Save. This brings you out of the config group popups. * Back on the Service page, the click on "Manage Config Groups". There's a duplicate entry for hdfs-01 * Click on the config group pulldown. There's a duplicate entry for hdfs-01 - see config_group_pulldown.png * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20201) Config Groups are shown twice after creation
[ https://issues.apache.org/jira/browse/AMBARI-20201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20201: - Attachment: config_group_pulldown.png > Config Groups are shown twice after creation > > > Key: AMBARI-20201 > URL: https://issues.apache.org/jira/browse/AMBARI-20201 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: config_group_pulldown.png > > > The same config group is being shown twice after config group creation. > Here's what I did: > * Go to Services > HDFS > Configs > * Click on "Manage Config Groups" > * There were two groups already (Default and AMS-DN) > * Added the 10 config groups hdfs-01, hdfs-02, ... hdfs-10 > * Clicked on hdfs-01 from the left panel > * Clicked on the + icon from the right panel > * Used the filter to set "perf-c-1" > * This added 111 hosts. Hit OK. Hit Save. This brings you out of the > config group popups. > * Back on the Service page, the click on "Manage Config Groups". There's a > duplicate entry for hdfs-01 > * Click on the config group pulldown. There's a duplicate entry for hdfs-01 > - see config_group_pulldown.png > * The duplicates go away after a page refresh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v3.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch, AMBARI-20200_branch-2.5_v3.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Attachment: (was: AMBARI-20197.patch)
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Status: Patch Available (was: Open)
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Attachment: AMBARI-20197.patch
Regenerated patch from the correct top level folder.
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch, AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated AMBARI-20197:
--
Status: Open (was: Patch Available)
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v2.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: (was: AMBARI-20200_branch-2.5_v2.patch) > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v2.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: (was: AMBARI-20200_branch-2.5_v2.patch) > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: (was: AMBARI-20200_branch-2.5_v2.patch) > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v2.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v2.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch, > AMBARI-20200_branch-2.5_v2.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Description: hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin's interpreter. As a result of which JDBC:phoenix on kerberos mode doesn't work. was:hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin's interpreter. > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. > As a result of which JDBC:phoenix on kerberos mode doesn't work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-20200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-20200: - Attachment: AMBARI-20200_branch-2.5_v1.patch > hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin > > > Key: AMBARI-20200 > URL: https://issues.apache.org/jira/browse/AMBARI-20200 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-20200_branch-2.5_v1.patch > > > hive-site.xml, hbase-site.xml, etc. are not found in class path for > Zeppelin's interpreter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20200) hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin
Prabhjyot Singh created AMBARI-20200: Summary: hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin Key: AMBARI-20200 URL: https://issues.apache.org/jira/browse/AMBARI-20200 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh hive-site.xml, hbase-site.xml, etc. are not found in class path for Zeppelin's interpreter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-17346) Dependent components should be shutdown before stopping hdfs
[ https://issues.apache.org/jira/browse/AMBARI-17346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-17346: Description: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. was: Sometimes admin shuts down hdfs first, then hbase. By the time hbase is shutdown, no data can be persisted (including metadata). This results in large number of inconsistencies when hbase cluster is brought back up. Before hdfs is shutdown, the components dependent on hdfs should be shutdown first. > Dependent components should be shutdown before stopping hdfs > > > Key: AMBARI-17346 > URL: https://issues.apache.org/jira/browse/AMBARI-17346 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > Sometimes admin shuts down hdfs first, then hbase. > By the time hbase is shutdown, no data can be persisted (including metadata). > This results in large number of inconsistencies when hbase cluster is brought > back up. > Before hdfs is shutdown, the components dependent on hdfs should be shutdown > first. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20197) RestMetricsPropertyProvider support nested JSON metrics
[
https://issues.apache.org/jira/browse/AMBARI-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884794#comment-15884794
]
Hadoop QA commented on AMBARI-20197:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854678/AMBARI-20197.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10760//console
This message is automatically generated.
> RestMetricsPropertyProvider support nested JSON metrics
> ---
>
> Key: AMBARI-20197
> URL: https://issues.apache.org/jira/browse/AMBARI-20197
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Affects Versions: 2.4.2
>Reporter: Kevin Risden
> Attachments: AMBARI-20197.patch
>
>
> Attempting to use the RestMetricsPropertyProvider with nested metrics results
> in a ClassCastException.
> {code}
> Caused by: java.lang.ClassCastException: com.google.gson.internal.StringMap
> cannot be cast to com.google.gson.JsonElement
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProvider.extractValuesFromJSON(RestMetricsPropertyProvider.java:472)
> {code}
> Based on reading the code, this should be supported by using the # path
> splitter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884792#comment-15884792
]
Hadoop QA commented on AMBARI-20199:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12854779/AMBARI-20199.2.branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10759//console
This message is automatically generated.
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.2.branch-2.5.patch,
> AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.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-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-20199:
--
Attachment: AMBARI-20199.2.branch-2.5.patch
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.2.branch-2.5.patch,
> AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.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)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
>
[jira] [Updated] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-20199:
--
Attachment: AMBARI-20199.branch-2.5.patch
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.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)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at
>
[jira] [Updated] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
[
https://issues.apache.org/jira/browse/AMBARI-20199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
DIPAYAN BHOWMICK updated AMBARI-20199:
--
Status: Patch Available (was: Open)
> Hive View: Query fails if we have an additional newline after the last query
> statement ending with ';'
> --
>
> Key: AMBARI-20199
> URL: https://issues.apache.org/jira/browse/AMBARI-20199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20199.branch-2.5.patch
>
>
> Suppose if I have a multiline query like this where the last statement ends
> with ';' and has an additional newline char
> {code:java}
> SELECT * FROM timesheet limit 5;
> SELECT * FROM drivers limit 5;
> {code}
> Then the query fails with following error:
> {code:java}
> org.apache.hive.service.cli.HiveSQLException: Error while compiling
> statement: FAILED: ParseException line 1:0 cannot recognize input near
> '' '' ''
> {code}
> entire trace:
> {code:java}
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error
> while compiling statement: FAILED: ParseException line 1:0 cannot recognize
> input near '' '' ''
> at
> org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
> at sun.reflect.GeneratedMethodAccessor697.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)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
> at
>
[jira] [Created] (AMBARI-20199) Hive View: Query fails if we have an additional newline after the last query statement ending with ';'
DIPAYAN BHOWMICK created AMBARI-20199:
-
Summary: Hive View: Query fails if we have an additional newline
after the last query statement ending with ';'
Key: AMBARI-20199
URL: https://issues.apache.org/jira/browse/AMBARI-20199
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
Priority: Critical
Fix For: 2.5.0
Suppose if I have a multiline query like this where the last statement ends
with ';' and has an additional newline char
{code:java}
SELECT * FROM timesheet limit 5;
SELECT * FROM drivers limit 5;
{code}
Then the query fails with following error:
{code:java}
org.apache.hive.service.cli.HiveSQLException: Error while compiling statement:
FAILED: ParseException line 1:0 cannot recognize input near '' ''
''
{code}
entire trace:
{code:java}
java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error while
compiling statement: FAILED: ParseException line 1:0 cannot recognize input
near '' '' ''
java.lang.Exception: org.apache.hive.service.cli.HiveSQLException: Error while
compiling statement: FAILED: ParseException line 1:0 cannot recognize input
near '' '' ''
at
org.apache.ambari.view.hive20.resources.jobs.JobService.getOne(JobService.java:146)
at sun.reflect.GeneratedMethodAccessor697.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)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
[jira] [Commented] (AMBARI-20198) [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image
[ https://issues.apache.org/jira/browse/AMBARI-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884782#comment-15884782 ] Hudson commented on AMBARI-20198: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6865 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6865/]) AMBARI-20198. [UT parallel tests] ambari maven execution needs external (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eb00261b807ec32e8a11d28f1deb282a2faf7ddb]) * (edit) ambari-project/pom.xml > [UT parallel tests] ambari maven execution needs external variable for > forkcount in docker image > > > Key: AMBARI-20198 > URL: https://issues.apache.org/jira/browse/AMBARI-20198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20198.patch > > > forkCount parameter for ambari-server UT is currently hardcoded to 1C and > cannot be overridden with -DforkCount. > We should be able to configure it, especially for runs in docker containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20198) [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image
[ https://issues.apache.org/jira/browse/AMBARI-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884781#comment-15884781 ] Hudson commented on AMBARI-20198: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1104 (See [https://builds.apache.org/job/Ambari-branch-2.5/1104/]) AMBARI-20198. [UT parallel tests] ambari maven execution needs external (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b426441d1cb77dfc2f78e0bca2767454deb3291e]) * (edit) ambari-project/pom.xml > [UT parallel tests] ambari maven execution needs external variable for > forkcount in docker image > > > Key: AMBARI-20198 > URL: https://issues.apache.org/jira/browse/AMBARI-20198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20198.patch > > > forkCount parameter for ambari-server UT is currently hardcoded to 1C and > cannot be overridden with -DforkCount. > We should be able to configure it, especially for runs in docker containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20198) [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image
[ https://issues.apache.org/jira/browse/AMBARI-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-20198. Resolution: Fixed Pushed to trunk and branch-2.5 > [UT parallel tests] ambari maven execution needs external variable for > forkcount in docker image > > > Key: AMBARI-20198 > URL: https://issues.apache.org/jira/browse/AMBARI-20198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20198.patch > > > forkCount parameter for ambari-server UT is currently hardcoded to 1C and > cannot be overridden with -DforkCount. > We should be able to configure it, especially for runs in docker containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20198) [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image
[ https://issues.apache.org/jira/browse/AMBARI-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi updated AMBARI-20198: --- Attachment: AMBARI-20198.patch > [UT parallel tests] ambari maven execution needs external variable for > forkcount in docker image > > > Key: AMBARI-20198 > URL: https://issues.apache.org/jira/browse/AMBARI-20198 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20198.patch > > > forkCount parameter for ambari-server UT is currently hardcoded to 1C and > cannot be overridden with -DforkCount. > We should be able to configure it, especially for runs in docker containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20198) [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image
Myroslav Papirkovskyi created AMBARI-20198: -- Summary: [UT parallel tests] ambari maven execution needs external variable for forkcount in docker image Key: AMBARI-20198 URL: https://issues.apache.org/jira/browse/AMBARI-20198 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Priority: Critical Fix For: 2.5.0 forkCount parameter for ambari-server UT is currently hardcoded to 1C and cannot be overridden with -DforkCount. We should be able to configure it, especially for runs in docker containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
