Oleg Nechiporenko created AMBARI-17911:
------------------------------------------
Summary: UI calls recommendation API, which returns an empty
string so value is invalid, yet UI doesn't show validation error for Atlas
configs
Key: AMBARI-17911
URL: https://issues.apache.org/jira/browse/AMBARI-17911
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Environment: ambari-server version: ambari-server-2.4.0.0-980.x86_64
ambari-server --hash: fce38bf0432f1d3db7772a0f303bb5e0c4cd8ae8
HDP Stack: 2.2
HDP Version: 2.5.0.0-934
Ambari DB: :MySQL
Oozie/Hive DB: MySQL/MySQL
Security:yes
Security Type:MIT/MIT
Blueprints: false
Umask:
JDK: OracleJDK7
HA: yes
OS: CentOS 6
Ambari User: root
Agents User: root
MOTD enabled: false
Customized service users: false
Is tmp exec: false
Reporter: Oleg Nechiporenko
Assignee: Oleg Nechiporenko
Priority: Critical
Fix For: 2.4.0
STR:
Install Ambari 2.4 with HDP 2.5, and attempt to add Atlas service without HBASE
or LogSearch (both of which are optional).
It calls http://server:8080/api/v1/stacks/HDP/versions/2.5/recommendations/###
, which then returns the correct response with a value of "" for several Atlas
configs
"atlas.audit.hbase.zookeeper.quorum" : ""
"atlas.graph.index.search.solr.zookeeper-url" : ""
Both of those configs actually require a value, so if you type in any text into
those textboxes and then press backspace to return to the original value of "",
then the UI shows a validation error.
I remember seeing this before, perhaps it is a regression.
Result: missing properties for Atlas
atlas.graph.index.search.solr.zookeeper-url and
atlas.audit.hbase.zookeeper.quorum
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
