[jira] [Updated] (AMBARI-23666) Hive Summary page does not have the correct 'Go To View' links.
[
https://issues.apache.org/jira/browse/AMBARI-23666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-23666:
--
Status: Patch Available (was: In Progress)
> Hive Summary page does not have the correct 'Go To View' links.
> ---
>
> Key: AMBARI-23666
> URL: https://issues.apache.org/jira/browse/AMBARI-23666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>Priority: Major
> Labels: pull-request-available
> Attachments: Before_Clicking_on_Go_To_View_Link.png,
> Hive_View_Go_To_Link_Issue.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> - When user access the Hive Summary page in the ambari 7.0 UI and click on
> the following "Go To View" links then they do not work properly and opens the
> Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
> {code}
> HIVE VIEW 2.0 "Go To View"
> DEBUG HIVE QUERY "Go To View"
> {code}
> Screenshots are attached:
> 1. Before_Clicking_on_Go_To_View_Link.png
> 2. When user clicks on the "Go To View" then we see
> "Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari
> Dashboard. http://$AMBARI_HOST:8080/#/main/dashboard/metrics
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23667) Cleanup/Fix Log Feeder patterns for HDP/HDF/smartsense etc.
Krisztian Kasa created AMBARI-23667: --- Summary: Cleanup/Fix Log Feeder patterns for HDP/HDF/smartsense etc. Key: AMBARI-23667 URL: https://issues.apache.org/jira/browse/AMBARI-23667 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23586) Cluster deployment fails if agent started after cluster creation request
[ https://issues.apache.org/jira/browse/AMBARI-23586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-23586: Resolution: Fixed Status: Resolved (was: Patch Available) > Cluster deployment fails if agent started after cluster creation request > > > Key: AMBARI-23586 > URL: https://issues.apache.org/jira/browse/AMBARI-23586 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-sever >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23666) Hive Summary page does not have the correct 'Go To View' links.
[
https://issues.apache.org/jira/browse/AMBARI-23666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23666:
Labels: pull-request-available (was: )
> Hive Summary page does not have the correct 'Go To View' links.
> ---
>
> Key: AMBARI-23666
> URL: https://issues.apache.org/jira/browse/AMBARI-23666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>Priority: Major
> Labels: pull-request-available
> Attachments: Before_Clicking_on_Go_To_View_Link.png,
> Hive_View_Go_To_Link_Issue.png
>
>
> - When user access the Hive Summary page in the ambari 7.0 UI and click on
> the following "Go To View" links then they do not work properly and opens the
> Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
> {code}
> HIVE VIEW 2.0 "Go To View"
> DEBUG HIVE QUERY "Go To View"
> {code}
> Screenshots are attached:
> 1. Before_Clicking_on_Go_To_View_Link.png
> 2. When user clicks on the "Go To View" then we see
> "Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari
> Dashboard. http://$AMBARI_HOST:8080/#/main/dashboard/metrics
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23666) Hive Summary page does not have the correct 'Go To View' links.
[
https://issues.apache.org/jira/browse/AMBARI-23666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-23666:
--
Description:
- When user access the Hive Summary page in the ambari 7.0 UI and click on the
following "Go To View" links then they do not work properly and opens the
Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
{code}
HIVE VIEW 2.0 "Go To View"
DEBUG HIVE QUERY "Go To View"
{code}
Screenshots are attached:
1. Before_Clicking_on_Go_To_View_Link.png
2. When user clicks on the "Go To View" then we see
"Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari Dashboard.
http://$AMBARI_HOST:8080/#/main/dashboard/metrics
was:
- When user access the Hive Summary page in the ambari 7.0 UI and click on the
following "Go To View" links then they do not work properly and opens the
Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
{code}
HIVE VIEW 2.0 "Go To View"
DEBUG HIVE QUERY "Go To View"
{code}
Screenshots are attached:
1. Before_Clicking_on_Go_To_View_Link.png
2. When user clicks on the "Go To View" then we see
"Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari Dashboard.
> Hive Summary page does not have the correct 'Go To View' links.
> ---
>
> Key: AMBARI-23666
> URL: https://issues.apache.org/jira/browse/AMBARI-23666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>Priority: Major
> Attachments: Before_Clicking_on_Go_To_View_Link.png,
> Hive_View_Go_To_Link_Issue.png
>
>
> - When user access the Hive Summary page in the ambari 7.0 UI and click on
> the following "Go To View" links then they do not work properly and opens the
> Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
> {code}
> HIVE VIEW 2.0 "Go To View"
> DEBUG HIVE QUERY "Go To View"
> {code}
> Screenshots are attached:
> 1. Before_Clicking_on_Go_To_View_Link.png
> 2. When user clicks on the "Go To View" then we see
> "Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari
> Dashboard. http://$AMBARI_HOST:8080/#/main/dashboard/metrics
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23666) Hive Summary page does not have the correct 'Go To View' links.
[
https://issues.apache.org/jira/browse/AMBARI-23666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-23666:
--
Description:
- When user access the Hive Summary page in the ambari 7.0 UI and click on the
following "Go To View" links then they do not work properly and opens the
Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
{code}
HIVE VIEW 2.0 "Go To View"
DEBUG HIVE QUERY "Go To View"
{code}
Screenshots are attached:
1. Before_Clicking_on_Go_To_View_Link.png
2. When user clicks on the "Go To View" then we see
"Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari Dashboard.
was:
- When user access the Hive Summary page in the ambari 7.0 UI and click on the
following "Go To View" links then they do not work properly and opens the
Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
{code}
HIVE VIEW 2.0 "Go To View"
DEBUG HIVE QUERY "Go To View"
{code}
Screenshots are attached:
1. Before_Clicking_on_Go_To_View_Link.png
2. When user clicks on the "Go To View" then we see
"Hive_View_Go_To_Link_Issue.png"
> Hive Summary page does not have the correct 'Go To View' links.
> ---
>
> Key: AMBARI-23666
> URL: https://issues.apache.org/jira/browse/AMBARI-23666
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk, 2.7.0
>Reporter: JaySenSharma
>Assignee: JaySenSharma
>Priority: Major
> Attachments: Before_Clicking_on_Go_To_View_Link.png,
> Hive_View_Go_To_Link_Issue.png
>
>
> - When user access the Hive Summary page in the ambari 7.0 UI and click on
> the following "Go To View" links then they do not work properly and opens the
> Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
> {code}
> HIVE VIEW 2.0 "Go To View"
> DEBUG HIVE QUERY "Go To View"
> {code}
> Screenshots are attached:
> 1. Before_Clicking_on_Go_To_View_Link.png
> 2. When user clicks on the "Go To View" then we see
> "Hive_View_Go_To_Link_Issue.png". The the URL changes back to Ambari
> Dashboard.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23666) Hive Summary page does not have the correct 'Go To View' links.
JaySenSharma created AMBARI-23666:
-
Summary: Hive Summary page does not have the correct 'Go To View'
links.
Key: AMBARI-23666
URL: https://issues.apache.org/jira/browse/AMBARI-23666
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: trunk, 2.7.0
Reporter: JaySenSharma
Assignee: JaySenSharma
Attachments: Before_Clicking_on_Go_To_View_Link.png,
Hive_View_Go_To_Link_Issue.png
- When user access the Hive Summary page in the ambari 7.0 UI and click on the
following "Go To View" links then they do not work properly and opens the
Ambari UI home page instead of taking to the Hive View UI or the Tez View UI.
{code}
HIVE VIEW 2.0 "Go To View"
DEBUG HIVE QUERY "Go To View"
{code}
Screenshots are attached:
1. Before_Clicking_on_Go_To_View_Link.png
2. When user clicks on the "Go To View" then we see
"Hive_View_Go_To_Link_Issue.png"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23665) ExecuteScript in resource_management is broken
[
https://issues.apache.org/jira/browse/AMBARI-23665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill updated AMBARI-23665:
Description:
When custom service script contains the following:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript(
code=constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
service installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/customservice.py",
line 82, in
CustomService().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/customservice.py",
line 36, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/customservice.py",
line 44, in configure
interpreter='/usr/bin/env python',
TypeError: __new__() takes at least 2 arguments (1 given)
{code}
When {{ExecuteScript}} is called like:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript('some-text',
code=constants.constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/customservice.py",
line 82, in
CustomService().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/customservice.py",
line 36, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/customservice.py",
line 44, in configure
interpreter='/usr/bin/env python',
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
277, in action_run
preexec_fn=_preexec_fn(self.resource))
NameError: global name '_preexec_fn' is not defined
{code}
was:
When custom service script contains the following:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript(
code=constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
service installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/hue.py",
line 82, in
Hue().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/hue.py",
line 36, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 44, in configure
interpreter='/usr/bin/env python',
TypeError: __new__() takes at least 2 arguments (1 given)
{code}
When {{ExecuteScript}} is called like:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript('some-text',
code=constants.constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 82, in
Hue().execute()
File
[jira] [Created] (AMBARI-23665) ExecuteScript in resource_management is broken
Kirill created AMBARI-23665:
---
Summary: ExecuteScript in resource_management is broken
Key: AMBARI-23665
URL: https://issues.apache.org/jira/browse/AMBARI-23665
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.6.1
Environment: Ambari 2.6.1.3 is installed as RPM from
[http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.6.1.3] but
the code in {{trunk}} looks the same:
https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/core/providers/system.py
Reporter: Kirill
When custom service script contains the following:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript(
code=constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
service installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/hue.py",
line 82, in
Hue().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/HUE/package/scripts/hue.py",
line 36, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 44, in configure
interpreter='/usr/bin/env python',
TypeError: __new__() takes at least 2 arguments (1 given)
{code}
When {{ExecuteScript}} is called like:
{code}
def configure(self, env, upgrade_type=None, config_dir=None):
import params
env.set_params(params)
ExecuteScript('some-text',
code=constants.constants.some_string,
interpreter='/usr/bin/env python',
)
{code}
installation fails with:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 82, in
Hue().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 36, in install
self.configure(env)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.6/services/CUSTOM_SERVICE/package/scripts/hue.py",
line 44, in configure
interpreter='/usr/bin/env python',
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
277, in action_run
preexec_fn=_preexec_fn(self.resource))
NameError: global name '_preexec_fn' is not defined
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23653) Ensure URLs to Ambari server resources are valid
[
https://issues.apache.org/jira/browse/AMBARI-23653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23653:
Labels: pull-request-available (was: )
> Ensure URLs to Ambari server resources are valid
>
>
> Key: AMBARI-23653
> URL: https://issues.apache.org/jira/browse/AMBARI-23653
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Ensure URLs to Ambari server resources are valid. For example, fix URLs like
> {noformat}
> http://ambari_server_host:8080/resources//DBConnectionVerification.jar
> {noformat}
> To
> {noformat}
> http://ambari_server_host:8080/resources/DBConnectionVerification.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23664) Update hadoop-env.sh to invoke DN kill script on Out of Memory exception
[ https://issues.apache.org/jira/browse/AMBARI-23664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru resolved AMBARI-23664. - Resolution: Won't Fix > Update hadoop-env.sh to invoke DN kill script on Out of Memory exception > - > > Key: AMBARI-23664 > URL: https://issues.apache.org/jira/browse/AMBARI-23664 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Hanisha Koneru >Priority: Major > > Scripts to kill the DataNode and NameNode on OOM condition are missing in HDP > 3.0 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23664) Update hadoop-env.sh to invoke DN kill script on Out of Memory exception
Hanisha Koneru created AMBARI-23664: --- Summary: Update hadoop-env.sh to invoke DN kill script on Out of Memory exception Key: AMBARI-23664 URL: https://issues.apache.org/jira/browse/AMBARI-23664 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Hanisha Koneru Scripts to kill the DataNode and NameNode on OOM condition are missing in HDP 3.0 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23663) Ensure URLs to Ambari server resources are valid
[
https://issues.apache.org/jira/browse/AMBARI-23663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23663:
--
Priority: Critical (was: Major)
> Ensure URLs to Ambari server resources are valid
>
>
> Key: AMBARI-23663
> URL: https://issues.apache.org/jira/browse/AMBARI-23663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.2
>
>
> Ensure URLs to Ambari server resources are valid. For example, fix URLs like
> {noformat}
> http://ambari_server_host:8080/resources//DBConnectionVerification.jar
> {noformat}
> To
> {noformat}
> http://ambari_server_host:8080/resources/DBConnectionVerification.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23653) Ensure URLs to Ambari server resources are valid
[
https://issues.apache.org/jira/browse/AMBARI-23653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23653:
--
Priority: Critical (was: Major)
> Ensure URLs to Ambari server resources are valid
>
>
> Key: AMBARI-23653
> URL: https://issues.apache.org/jira/browse/AMBARI-23653
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.7.0
>
>
> Ensure URLs to Ambari server resources are valid. For example, fix URLs like
> {noformat}
> http://ambari_server_host:8080/resources//DBConnectionVerification.jar
> {noformat}
> To
> {noformat}
> http://ambari_server_host:8080/resources/DBConnectionVerification.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23663) Ensure URLs to Ambari server resources are valid
[
https://issues.apache.org/jira/browse/AMBARI-23663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23663:
--
Fix Version/s: (was: 2.7.0)
2.6.2
> Ensure URLs to Ambari server resources are valid
>
>
> Key: AMBARI-23663
> URL: https://issues.apache.org/jira/browse/AMBARI-23663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.6.2
>
>
> Ensure URLs to Ambari server resources are valid. For example, fix URLs like
> {noformat}
> http://ambari_server_host:8080/resources//DBConnectionVerification.jar
> {noformat}
> To
> {noformat}
> http://ambari_server_host:8080/resources/DBConnectionVerification.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23663) Ensure URLs to Ambari server resources are valid
Robert Levas created AMBARI-23663:
-
Summary: Ensure URLs to Ambari server resources are valid
Key: AMBARI-23663
URL: https://issues.apache.org/jira/browse/AMBARI-23663
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.2.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.0
Ensure URLs to Ambari server resources are valid. For example, fix URLs like
{noformat}
http://ambari_server_host:8080/resources//DBConnectionVerification.jar
{noformat}
To
{noformat}
http://ambari_server_host:8080/resources/DBConnectionVerification.jar
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23653) Ensure URLs to Ambari server resources are valid
[
https://issues.apache.org/jira/browse/AMBARI-23653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-23653:
--
Affects Version/s: (was: 2.7.0)
1.2.0
> Ensure URLs to Ambari server resources are valid
>
>
> Key: AMBARI-23653
> URL: https://issues.apache.org/jira/browse/AMBARI-23653
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 1.2.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
>
> Ensure URLs to Ambari server resources are valid. For example, fix URLs like
> {noformat}
> http://ambari_server_host:8080/resources//DBConnectionVerification.jar
> {noformat}
> To
> {noformat}
> http://ambari_server_host:8080/resources/DBConnectionVerification.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23659) Add a configuration "metastore.catalog.default=spark" in hive-site.xml for Spark
[
https://issues.apache.org/jira/browse/AMBARI-23659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-23659.
Resolution: Fixed
> Add a configuration "metastore.catalog.default=spark" in hive-site.xml for
> Spark
>
>
> Key: AMBARI-23659
> URL: https://issues.apache.org/jira/browse/AMBARI-23659
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Major
> Fix For: 2.7.0
>
>
> {{metastore.catalog.default}} is a configuration in Hive 3.x, and its default
> value is "hive". Recently we added the new Hive metastore 3.0.0 support for
> Spark, so {{metastore.catalog.default}} should be set to "spark" in
> hive-site.xml for Spark.
> *metastore.catalog.default=spark*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23662) Log Search UI: subscription error on route changing
Istvan Tobias created AMBARI-23662: -- Summary: Log Search UI: subscription error on route changing Key: AMBARI-23662 URL: https://issues.apache.org/jira/browse/AMBARI-23662 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Fix For: 2.7.0 Changing route from Shipper Configuration to Logs causes break of the application. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23661) Support POST for querying logs for Log Search REST API
Olivér Szabó created AMBARI-23661: - Summary: Support POST for querying logs for Log Search REST API Key: AMBARI-23661 URL: https://issues.apache.org/jira/browse/AMBARI-23661 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23652) LogFeeder: lowercase cluster name (writing docs & znode generation)
[ https://issues.apache.org/jira/browse/AMBARI-23652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23652. --- Resolution: Fixed > LogFeeder: lowercase cluster name (writing docs & znode generation) > --- > > Key: AMBARI-23652 > URL: https://issues.apache.org/jira/browse/AMBARI-23652 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23651) Infra Solr / Logsearch: debian9 support
[ https://issues.apache.org/jira/browse/AMBARI-23651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23651. --- Resolution: Fixed > Infra Solr / Logsearch: debian9 support > --- > > Key: AMBARI-23651 > URL: https://issues.apache.org/jira/browse/AMBARI-23651 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23660) Hosts topology can be incomplete for components install during blueprint deploy
[ https://issues.apache.org/jira/browse/AMBARI-23660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23660: Labels: pull-request-available (was: ) > Hosts topology can be incomplete for components install during blueprint > deploy > --- > > Key: AMBARI-23660 > URL: https://issues.apache.org/jira/browse/AMBARI-23660 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Execution command should contain actual cluster topology information. > Temporary fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23660) Hosts topology can be incomplete for components install during blueprint deploy
Myroslav Papirkovskyi created AMBARI-23660: -- Summary: Hosts topology can be incomplete for components install during blueprint deploy Key: AMBARI-23660 URL: https://issues.apache.org/jira/browse/AMBARI-23660 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.0 Execution command should contain actual cluster topology information. Temporary fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23648) Log Search UI: Various fixes for Shipper Configuration
[ https://issues.apache.org/jira/browse/AMBARI-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23648: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search UI: Various fixes for Shipper Configuration > -- > > Key: AMBARI-23648 > URL: https://issues.apache.org/jira/browse/AMBARI-23648 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 48h > Time Spent: 24.5h > Remaining Estimate: 23.5h > > * Validation for the component name in test form should revalidate when the > config JSON has changed > * The navigation got extra two URL when the cluster and/or the service name > is not provided. It should redirect directly to the right URL > * Notifications styling should be better -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23648) Log Search UI: Various fixes for Shipper Configuration
[ https://issues.apache.org/jira/browse/AMBARI-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23648: --- Status: Patch Available (was: Open) > Log Search UI: Various fixes for Shipper Configuration > -- > > Key: AMBARI-23648 > URL: https://issues.apache.org/jira/browse/AMBARI-23648 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 48h > Time Spent: 0.5h > Remaining Estimate: 47.5h > > * Validation for the component name in test form should revalidate when the > config JSON has changed > * The navigation got extra two URL when the cluster and/or the service name > is not provided. It should redirect directly to the right URL > * Notifications styling should be better -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23659) Add a configuration "metastore.catalog.default=spark" in hive-site.xml for Spark
Vitaly Brodetskyi created AMBARI-23659:
--
Summary: Add a configuration "metastore.catalog.default=spark" in
hive-site.xml for Spark
Key: AMBARI-23659
URL: https://issues.apache.org/jira/browse/AMBARI-23659
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Fix For: 2.7.0
{{metastore.catalog.default}} is a configuration in Hive 3.x, and its default
value is "hive". Recently we added the new Hive metastore 3.0.0 support for
Spark, so {{metastore.catalog.default}} should be set to "spark" in
hive-site.xml for Spark.
*metastore.catalog.default=spark*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23657) Ambari-agent should handle delivery status responses from server
[ https://issues.apache.org/jira/browse/AMBARI-23657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448097#comment-16448097 ] Hudson commented on AMBARI-23657: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9103 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9103/]) AMBARI-23657. Ambari-agent should handle delivery status responses from (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b22d22c556f50d58ac597a7636f4d3dd9bd192aa]) * (edit) ambari-agent/src/main/python/ambari_agent/listeners/ServerResponsesListener.py * (edit) ambari-agent/src/main/python/ambari_agent/HostStatusReporter.py * (edit) ambari-agent/src/main/python/ambari_agent/CommandStatusDict.py * (edit) ambari-agent/src/main/python/ambari_agent/HeartbeatThread.py * (edit) ambari-agent/src/main/python/ambari_agent/AlertStatusReporter.py * (edit) ambari-agent/src/main/python/ambari_agent/InitializerModule.py * (edit) ambari-agent/src/main/python/ambari_agent/ComponentStatusExecutor.py > Ambari-agent should handle delivery status responses from server > > > Key: AMBARI-23657 > URL: https://issues.apache.org/jira/browse/AMBARI-23657 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23657.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This is required so that if connection between agent and server is lost, agent > knows what was lost and can resend it later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23658) No widgets displayed on dashboard after adding third NameNode namespace
[
https://issues.apache.org/jira/browse/AMBARI-23658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448095#comment-16448095
]
Hudson commented on AMBARI-23658:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9103 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9103/])
AMBARI-23658 No widgets displayed on dashboard after adding third (ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=4b22a9b1642097bcaec1f69b1d7cc30fcea7f508])
* (edit) ambari-web/app/views/main/dashboard/widgets.js
> No widgets displayed on dashboard after adding third NameNode namespace
> ---
>
> Key: AMBARI-23658
> URL: https://issues.apache.org/jira/browse/AMBARI-23658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After enabling NameNode federation and adding two additional namespaces,
> dashboards has no widgets displayed, with infinite spinner instead of them.
> Also, JS error is thrown: {{Uncaught TypeError: Cannot read property '1' of
> undefined}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23648) Log Search UI: Various fixes for Shipper Configuration
[ https://issues.apache.org/jira/browse/AMBARI-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448096#comment-16448096 ] Hudson commented on AMBARI-23648: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9103 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9103/]) [AMBARI-23648] - Log Search UI: Various fixes for Shipper Configuration (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f9429ae6868beb3cd51659cda4ce5c1f5741fea4]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/components/shipper-configuration/shipper-configuration.component.less * (add) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/services/shipper.guard.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/shipper.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/services/notification.service.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/directives/validator.directive.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shared/notifications.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/shipper-routing.module.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/components/shipper-configuration/shipper-configuration.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/components/shipper-service-configuration-form/shipper-service-configuration-form.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/modules/shipper/components/shipper-service-configuration-form/shipper-service-configuration-form.component.html > Log Search UI: Various fixes for Shipper Configuration > -- > > Key: AMBARI-23648 > URL: https://issues.apache.org/jira/browse/AMBARI-23648 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 48h > Time Spent: 0.5h > Remaining Estimate: 47.5h > > * Validation for the component name in test form should revalidate when the > config JSON has changed > * The navigation got extra two URL when the cluster and/or the service name > is not provided. It should redirect directly to the right URL > * Notifications styling should be better -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23620) Oozie - JDBC Driver class does not change when the Database type is changed
[ https://issues.apache.org/jira/browse/AMBARI-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Molnar reassigned AMBARI-23620: -- Assignee: Sandor Molnar > Oozie - JDBC Driver class does not change when the Database type is changed > --- > > Key: AMBARI-23620 > URL: https://issues.apache.org/jira/browse/AMBARI-23620 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: db-config-issues.mov > > Time Spent: 20m > Remaining Estimate: 0h > > In ambari 2.7.0.0-330, when the database type is changed for Oozie service, > the JDBC server class does not change. This happens in the install wizard as > well as post-install. > The behavior is different in Hive, where the JDBC server class changes when > the database type changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23620) Oozie - JDBC Driver class does not change when the Database type is changed
[ https://issues.apache.org/jira/browse/AMBARI-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448068#comment-16448068 ] Sandor Molnar commented on AMBARI-23620: The issue is that there is no service advisor for Oozie in HDP 3. I created one and will submit soon into hdp_ambari_definitions but PR 1072 needs to be merged first. > Oozie - JDBC Driver class does not change when the Database type is changed > --- > > Key: AMBARI-23620 > URL: https://issues.apache.org/jira/browse/AMBARI-23620 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: db-config-issues.mov > > Time Spent: 20m > Remaining Estimate: 0h > > In ambari 2.7.0.0-330, when the database type is changed for Oozie service, > the JDBC server class does not change. This happens in the install wizard as > well as post-install. > The behavior is different in Hive, where the JDBC server class changes when > the database type changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23620) Oozie - JDBC Driver class does not change when the Database type is changed
[ https://issues.apache.org/jira/browse/AMBARI-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23620: Labels: pull-request-available (was: ) > Oozie - JDBC Driver class does not change when the Database type is changed > --- > > Key: AMBARI-23620 > URL: https://issues.apache.org/jira/browse/AMBARI-23620 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: db-config-issues.mov > > > In ambari 2.7.0.0-330, when the database type is changed for Oozie service, > the JDBC server class does not change. This happens in the install wizard as > well as post-install. > The behavior is different in Hive, where the JDBC server class changes when > the database type changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23656) NameNode namespaces aren't sorted by name
[ https://issues.apache.org/jira/browse/AMBARI-23656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16448033#comment-16448033 ] Hudson commented on AMBARI-23656: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9102 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9102/]) AMBARI-23656 NameNode namespaces aren't sorted by name. (ababiichuk) (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=abb0a05a104ceb534b2866c508dee38b7caf2737]) * (edit) ambari-web/app/models/service/hdfs.js * (edit) ambari-web/app/views/main/service/info/summary.js > NameNode namespaces aren't sorted by name > - > > Key: AMBARI-23656 > URL: https://issues.apache.org/jira/browse/AMBARI-23656 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Namespaces should be displayed in alphabetical order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23658) No widgets displayed on dashboard after adding third NameNode namespace
[
https://issues.apache.org/jira/browse/AMBARI-23658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk resolved AMBARI-23658.
---
Resolution: Fixed
Merged to trunk
> No widgets displayed on dashboard after adding third NameNode namespace
> ---
>
> Key: AMBARI-23658
> URL: https://issues.apache.org/jira/browse/AMBARI-23658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After enabling NameNode federation and adding two additional namespaces,
> dashboards has no widgets displayed, with infinite spinner instead of them.
> Also, JS error is thrown: {{Uncaught TypeError: Cannot read property '1' of
> undefined}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23651) Infra Solr / Logsearch: debian9 support
[ https://issues.apache.org/jira/browse/AMBARI-23651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447982#comment-16447982 ] Hudson commented on AMBARI-23651: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9101 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9101/]) AMBARI-23651. Infra Solr / Logsearch: debian9 support. (#1065) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=92630b7dfdc50f243da8db2184e372b6a0a0ec5f]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml > Infra Solr / Logsearch: debian9 support > --- > > Key: AMBARI-23651 > URL: https://issues.apache.org/jira/browse/AMBARI-23651 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23656) NameNode namespaces aren't sorted by name
[ https://issues.apache.org/jira/browse/AMBARI-23656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-23656. --- Resolution: Fixed Merged to trunk > NameNode namespaces aren't sorted by name > - > > Key: AMBARI-23656 > URL: https://issues.apache.org/jira/browse/AMBARI-23656 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Namespaces should be displayed in alphabetical order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23658) No widgets displayed on dashboard after adding third NameNode namespace
[
https://issues.apache.org/jira/browse/AMBARI-23658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23658:
Labels: pull-request-available (was: )
> No widgets displayed on dashboard after adding third NameNode namespace
> ---
>
> Key: AMBARI-23658
> URL: https://issues.apache.org/jira/browse/AMBARI-23658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> After enabling NameNode federation and adding two additional namespaces,
> dashboards has no widgets displayed, with infinite spinner instead of them.
> Also, JS error is thrown: {{Uncaught TypeError: Cannot read property '1' of
> undefined}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23658) No widgets displayed on dashboard after adding third NameNode namespace
Andrii Babiichuk created AMBARI-23658:
-
Summary: No widgets displayed on dashboard after adding third
NameNode namespace
Key: AMBARI-23658
URL: https://issues.apache.org/jira/browse/AMBARI-23658
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Fix For: 2.7.0
After enabling NameNode federation and adding two additional namespaces,
dashboards has no widgets displayed, with infinite spinner instead of them.
Also, JS error is thrown: {{Uncaught TypeError: Cannot read property '1' of
undefined}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23652) LogFeeder: lowercase cluster name (writing docs & znode generation)
[ https://issues.apache.org/jira/browse/AMBARI-23652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447900#comment-16447900 ] Hudson commented on AMBARI-23652: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9100 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9100/]) AMBARI-23652. LogFeeder: lowercase cluster name (writing docs & znode (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=baff299f3902b8e9e160616d2a935bed11f0b04d]) * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/LogSearchConfigFactory.java * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java > LogFeeder: lowercase cluster name (writing docs & znode generation) > --- > > Key: AMBARI-23652 > URL: https://issues.apache.org/jira/browse/AMBARI-23652 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23657) Ambari-agent should handle delivery status responses from server
[ https://issues.apache.org/jira/browse/AMBARI-23657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23657: Labels: pull-request-available (was: ) > Ambari-agent should handle delivery status responses from server > > > Key: AMBARI-23657 > URL: https://issues.apache.org/jira/browse/AMBARI-23657 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23657.patch > > > This is required so that if connection between agent and server is lost, agent > knows what was lost and can resend it later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23657) Ambari-agent should handle delivery status responses from server
Andrew Onischuk created AMBARI-23657: Summary: Ambari-agent should handle delivery status responses from server Key: AMBARI-23657 URL: https://issues.apache.org/jira/browse/AMBARI-23657 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23657.patch This is required so that if connection between agent and server is lost, agent knows what was lost and can resend it later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23657) Ambari-agent should handle delivery status responses from server
[ https://issues.apache.org/jira/browse/AMBARI-23657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23657: - Attachment: AMBARI-23657.patch > Ambari-agent should handle delivery status responses from server > > > Key: AMBARI-23657 > URL: https://issues.apache.org/jira/browse/AMBARI-23657 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23657.patch > > > This is required so that if connection between agent and server is lost, agent > knows what was lost and can resend it later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23657) Ambari-agent should handle delivery status responses from server
[ https://issues.apache.org/jira/browse/AMBARI-23657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23657: - Status: Patch Available (was: Open) > Ambari-agent should handle delivery status responses from server > > > Key: AMBARI-23657 > URL: https://issues.apache.org/jira/browse/AMBARI-23657 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23657.patch > > > This is required so that if connection between agent and server is lost, agent > knows what was lost and can resend it later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23656) NameNode namespaces aren't sorted by name
[ https://issues.apache.org/jira/browse/AMBARI-23656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23656: Labels: pull-request-available (was: ) > NameNode namespaces aren't sorted by name > - > > Key: AMBARI-23656 > URL: https://issues.apache.org/jira/browse/AMBARI-23656 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Namespaces should be displayed in alphabetical order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23656) NameNode namespaces aren't sorted by name
Andrii Babiichuk created AMBARI-23656: - Summary: NameNode namespaces aren't sorted by name Key: AMBARI-23656 URL: https://issues.apache.org/jira/browse/AMBARI-23656 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 Namespaces should be displayed in alphabetical order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21858) Not able to enable hive "Interactive Query"
[
https://issues.apache.org/jira/browse/AMBARI-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-21858:
Labels: pull-request-available (was: )
> Not able to enable hive "Interactive Query"
> ---
>
> Key: AMBARI-21858
> URL: https://issues.apache.org/jira/browse/AMBARI-21858
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Assignee: Akhil S Naik
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> when try to enable Hive interactive query it fails with below JS error and
> Save button does not get activated and does not start any wizard.
> {noformat}
> app.js:42734 Uncaught TypeError: Cannot read property 'forEach' of
> undefined(…)(anonymous function) @
> app.js:42734pendingBatchRequestsAjaxSuccess @ app.js:42733opt.success @
> app.js:175507o @ vendor.js:106fireWith @ vendor.js:106w @ vendor.js:108d @
> vendor.js:108
> {noformat}
> Workaround: Update requestschedule table to mark the entry as "COMPLETED" to
> resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-19820) ViewFS Support for Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447609#comment-16447609
]
Hyun Jay, Lee edited comment on AMBARI-19820 at 4/23/18 7:10 AM:
-
I found forbidding codes of JS as follows.
[https://github.com/hortonworks/ambari-release/blob/AMBARI-2.5.2.0-298-tag/ambari-web/app/utils/validator.js#L181-L191]
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after changing the above codes to allow '/' and found that it
worked well.
However, it was applied to only the browser-side. And it didn't save the viewFS
path to Ambari's database when I clicked 'Save' button.
I think other codes of server-side might still forbid user from setting '/'. :(
I'm not good at javascript and node.js. so, I hope some fluent user of node.js
would resolve this.
was (Author: hyunjay.lee):
I found the forbidding code of JS as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after changing the above codes and found that it worked well.
However, it was applied to only the browser-side. And it wasn't saved to
Ambari's database when I clicked 'Save' button.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
> ViewFS Support for Ambari
> -
>
> Key: AMBARI-19820
> URL: https://issues.apache.org/jira/browse/AMBARI-19820
> Project: Ambari
> Issue Type: Wish
> Components: 2.2.1
>Reporter: Keith Manthey
>Priority: Minor
>
> Allow the creation of ViewFS mount points in the custom core-site.xml area
> for HDFS. Currently, the ViewFS mount points contain banned characters in
> entry (/) for Ambari in the Key. Example of a ViewFS mount point Key =
> "fs.viewfs.mounttable.[zone].link./[mount]". The value would be an IP / FQDN
> with path ("hdfs://10.111.156.210:8020/user/")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-21858) Not able to enable hive "Interactive Query"
[
https://issues.apache.org/jira/browse/AMBARI-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik reassigned AMBARI-21858:
-
Assignee: Akhil S Naik
> Not able to enable hive "Interactive Query"
> ---
>
> Key: AMBARI-21858
> URL: https://issues.apache.org/jira/browse/AMBARI-21858
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Assignee: Akhil S Naik
>Priority: Critical
> Fix For: 3.0.0
>
>
> when try to enable Hive interactive query it fails with below JS error and
> Save button does not get activated and does not start any wizard.
> {noformat}
> app.js:42734 Uncaught TypeError: Cannot read property 'forEach' of
> undefined(…)(anonymous function) @
> app.js:42734pendingBatchRequestsAjaxSuccess @ app.js:42733opt.success @
> app.js:175507o @ vendor.js:106fireWith @ vendor.js:106w @ vendor.js:108d @
> vendor.js:108
> {noformat}
> Workaround: Update requestschedule table to mark the entry as "COMPLETED" to
> resolve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
Vivek Rathod created AMBARI-23655:
-
Summary: While adding HDFS Namespace from UI, Timeline service
fails to start
Key: AMBARI-23655
URL: https://issues.apache.org/jira/browse/AMBARI-23655
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Vivek Rathod
Fix For: 2.7.0
While adding HDFS Namespace from UI, Timeline service fails to start in the
last step ("Restart All Services") because the active Namenode(from older
namespace) is in Safe Mode
It seems for restart all service operation we do not wait for namenode to leave
safemode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-19820) ViewFS Support for Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447609#comment-16447609
]
Hyun Jay, Lee edited comment on AMBARI-19820 at 4/23/18 6:07 AM:
-
I found the forbidding code of JS as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after changing the above codes and found that it worked well.
However, it was applied to only the browser-side. And it wasn't saved to
Ambari's database when I clicked 'Save' button.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
was (Author: hyunjay.lee):
I found the forbidding code of JS as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after change the above codes and found it worked well.
However, it was applied only to the browser-side. And it wasn't saved to
Ambari's database.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
> ViewFS Support for Ambari
> -
>
> Key: AMBARI-19820
> URL: https://issues.apache.org/jira/browse/AMBARI-19820
> Project: Ambari
> Issue Type: Wish
> Components: 2.2.1
>Reporter: Keith Manthey
>Priority: Minor
>
> Allow the creation of ViewFS mount points in the custom core-site.xml area
> for HDFS. Currently, the ViewFS mount points contain banned characters in
> entry (/) for Ambari in the Key. Example of a ViewFS mount point Key =
> "fs.viewfs.mounttable.[zone].link./[mount]". The value would be an IP / FQDN
> with path ("hdfs://10.111.156.210:8020/user/")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-19820) ViewFS Support for Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447609#comment-16447609
]
Hyun Jay, Lee edited comment on AMBARI-19820 at 4/23/18 6:05 AM:
-
I found the forbidding code of JS as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after change the above codes and found it worked well.
However, it was applied only to the browser-side. And it wasn't saved to
Ambari's database.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
was (Author: hyunjay.lee):
I found the forbidden code of JS side as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after change the above codes and found it worked well.
However, it was applied only to the browser-side. And it wasn't saved to
Ambari's database.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
> ViewFS Support for Ambari
> -
>
> Key: AMBARI-19820
> URL: https://issues.apache.org/jira/browse/AMBARI-19820
> Project: Ambari
> Issue Type: Wish
> Components: 2.2.1
>Reporter: Keith Manthey
>Priority: Minor
>
> Allow the creation of ViewFS mount points in the custom core-site.xml area
> for HDFS. Currently, the ViewFS mount points contain banned characters in
> entry (/) for Ambari in the Key. Example of a ViewFS mount point Key =
> "fs.viewfs.mounttable.[zone].link./[mount]". The value would be an IP / FQDN
> with path ("hdfs://10.111.156.210:8020/user/")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-19820) ViewFS Support for Ambari
[
https://issues.apache.org/jira/browse/AMBARI-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447609#comment-16447609
]
Hyun Jay, Lee commented on AMBARI-19820:
I found the forbidden code of JS side as follows.
{code:java}
$> vi /usr/lib/ambari-server/web/javascripts/app.js
…
190551 /**
190552 * validate key of configurations
190553 * allow spaces as prefix and suffix
190554 *
190555 * @param value
190556 * @return {Boolean}
190557 */
190558 isValidConfigKey: function(value) {
190559 var configKeyRegex = /^\s*[0-9a-z_\-\.\*\/]+\s*$/i;
190560 return configKeyRegex.test(value);
190561 },
…
{code}
And I tried after change the above codes and found it worked well.
However, it was applied only to the browser-side. And it wasn't saved to
Ambari's database.
I think other codes of server-side would still forbid user from setting '/'. :(
I'm not good at node.js. so, I hope some fluent user of node.js would resolve
this.
> ViewFS Support for Ambari
> -
>
> Key: AMBARI-19820
> URL: https://issues.apache.org/jira/browse/AMBARI-19820
> Project: Ambari
> Issue Type: Wish
> Components: 2.2.1
>Reporter: Keith Manthey
>Priority: Minor
>
> Allow the creation of ViewFS mount points in the custom core-site.xml area
> for HDFS. Currently, the ViewFS mount points contain banned characters in
> entry (/) for Ambari in the Key. Example of a ViewFS mount point Key =
> "fs.viewfs.mounttable.[zone].link./[mount]". The value would be an IP / FQDN
> with path ("hdfs://10.111.156.210:8020/user/")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
