[jira] [Resolved] (AMBARI-24910) Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
[ https://issues.apache.org/jira/browse/AMBARI-24910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24910. -- Resolution: Fixed > Grafana: Fix for Storm Components and Storm Kafka Offset dashboards > --- > > Key: AMBARI-24910 > URL: https://issues.apache.org/jira/browse/AMBARI-24910 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > These two dashboards error out if no data point is provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24908) OneFS mpack should include webhdfs enable setting - Default Enabled
[ https://issues.apache.org/jira/browse/AMBARI-24908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24908: Labels: pull-request-available (was: ) > OneFS mpack should include webhdfs enable setting - Default Enabled > --- > > Key: AMBARI-24908 > URL: https://issues.apache.org/jira/browse/AMBARI-24908 > Project: Ambari > Issue Type: Bug > Components: ambari-server, contrib >Affects Versions: 3.0.0 > Environment: HDP 3.0 and Isilon 8.2.0 >Reporter: Andrew Huff >Priority: Major > Labels: pull-request-available > Original Estimate: 2h > Remaining Estimate: 2h > > The Isilon management pack should include the 'dfs.webhdfs.enabled' > configuration in the hdfs_site.xml file as it is needed by the Ambari Agent. > This previous Jira incorrectly removed the setting which was originally set > to 'false', however, Isilon has since increased its support for WebHDFS. The > previous Jira assumed that by removing the setting the Ambari Agent would > default to 'true' for this setting. This does not appear to be the case. > https://issues.apache.org/jira/browse/AMBARI-24539 > https://github.com/apache/ambari/pull/2170 > This setting needs to be added back to the Isilon management pack with a > default value of 'true'. This value should also be user configurable > 'overrideable = true'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-2491) Security Wizard: show which principals and keytabs need to be created on which hosts
[
https://issues.apache.org/jira/browse/AMBARI-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689875#comment-16689875
]
Hudson commented on AMBARI-2491:
SUCCESS: Integrated in Jenkins build Ambari-Metrics-master-Commit #15 (See
[https://builds.apache.org/job/Ambari-Metrics-master-Commit/15/])
[AMBARI-2491] Grafana: Fix for Storm Components and Storm Kafka Offset
(ishanbhatt.1989:
[https://gitbox.apache.org/repos/asf?p=ambari-metrics.git=commit=70018585c8ad67f663c1092d8f03bffb6d6ec3a2])
* (edit) ambari-metrics-grafana/ambari-metrics/datasource.js
> Security Wizard: show which principals and keytabs need to be created on
> which hosts
>
>
> Key: AMBARI-2491
> URL: https://issues.apache.org/jira/browse/AMBARI-2491
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
>Affects Versions: 1.2.5
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 1.2.5
>
> Attachments: AMBARI-2491.patch,
> host-component-principal-keytab-display.png
>
>
> Currently it is very difficult to know what principals and keytabs need to be
> created on which hosts.
> We should present this information to the end user in a format that is easy
> to consume.
> The user running the wizard may not be the one who will be creating keytabs
> and principals. We can expose the capability to download a csv file and send
> it to the appropriate person who may parse the data to create a script to
> generate principals/keytabs (or do so manually).
> Display the attached as a popup after Configure Services step is done.
> Let's show it as a popup so that we don't affect any existing navigation/flow.
> For generating the content:
> Keytab paths are based on the user input
> Principal names are based on the user input
> NameNode host: show the nn and HTTP principals and keytab paths
> JobTracker host: show the jt principal and keytab path
> Oozie Server host: show the oozie and HTTP principals and keytab paths
> Nagios Server host: show the nagios principal and keytab path
> HBase Master host: show the hbase principal and keytab path
> Hive Server host: show the hive principal and keytab path
> WebHCat Server host: show the HTTP principal and keytab path
> ZooKeeper Server host: show the zookeeper principal and keytab path
> DataNode host: show the dn principal and keytab path
> TaskTracker host: show the tt principal and keytab path
> RegionServer host: show the hbase principal and keytab path
> If there are duplicated principals on the same host, display it only once.
> Clickng on "Download CSV" downloads the CSV file
> ("host-principal-keytab-list.csv"). The same content, except each row is a
> comma-delimited list with a \n at the end.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24910) Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
[ https://issues.apache.org/jira/browse/AMBARI-24910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24910: Labels: pull-request-available (was: ) > Grafana: Fix for Storm Components and Storm Kafka Offset dashboards > --- > > Key: AMBARI-24910 > URL: https://issues.apache.org/jira/browse/AMBARI-24910 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > These two dashboards error out if no data point is provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24910) Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
[
https://issues.apache.org/jira/browse/AMBARI-24910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689852#comment-16689852
]
ASF GitHub Bot commented on AMBARI-24910:
-
ishanbha closed pull request #11: [AMBARI-24910] Grafana: Fix for Storm
Components and Storm Kafka Offse…
URL: https://github.com/apache/ambari-metrics/pull/11
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-metrics-grafana/ambari-metrics/datasource.js
b/ambari-metrics-grafana/ambari-metrics/datasource.js
index c6885da..dd64566 100644
--- a/ambari-metrics-grafana/ambari-metrics/datasource.js
+++ b/ambari-metrics-grafana/ambari-metrics/datasource.js
@@ -642,8 +642,8 @@ define([
//Templatized Dashboards for Storm Components
if (templateSrv.variables[0].query === "topologies" &&
templateSrv.variables[1] &&
templateSrv.variables[1].name === "component") {
-var selectedTopology = templateSrv._values.topologies;
-var selectedComponent = templateSrv._values.component;
+var selectedTopology =
templateSrv.index.topologies.options[0].value || "";
+var selectedComponent = templateSrv.index.component.options[0] ?
templateSrv.index.component.options[0].value : "";
metricsPromises.push(_.map(options.targets, function (target) {
target.sTopology = selectedTopology;
target.sComponent = selectedComponent;
@@ -655,8 +655,8 @@ define([
//Templatized Dashboard for Storm Kafka Offset
if (templateSrv.variables[0].query === "topologies" &&
templateSrv.variables[1] &&
templateSrv.variables[1].name === "topic") {
-var selectedTopology = templateSrv._values.topologies;
-var selectedTopic = templateSrv._values.topic;
+var selectedTopology =
templateSrv.index.topologies.options[0].value || "";
+var selectedTopic = templateSrv.index.topic.options[0] ?
templateSrv.index.topic.options[0].value : "";
metricsPromises.push(_.map(options.targets, function (target) {
target.sTopology = selectedTopology;
target.sTopic = selectedTopic;
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
> ---
>
> Key: AMBARI-24910
> URL: https://issues.apache.org/jira/browse/AMBARI-24910
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
>
> These two dashboards error out if no data point is provided.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689697#comment-16689697 ] ASF GitHub Bot commented on AMBARI-24833: - asfgit commented on issue #26: AMBARI-24833. Support for cloud logs to using filters + JSON output URL: https://github.com/apache/ambari-logsearch/pull/26#issuecomment-439465913 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/54/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689628#comment-16689628 ] ASF GitHub Bot commented on AMBARI-24833: - asfgit commented on issue #26: AMBARI-24833. Support for cloud logs to using filters + JSON output URL: https://github.com/apache/ambari-logsearch/pull/26#issuecomment-439447527 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/53/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689622#comment-16689622 ] ASF GitHub Bot commented on AMBARI-24833: - oleewere opened a new pull request #26: AMBARI-24833. Support for cloud logs to using filters + JSON output URL: https://github.com/apache/ambari-logsearch/pull/26 # What changes were proposed in this pull request? - optionally use filters (+ json output) for logs that will be archived to cloud storage (default: false) - create output enricher class - only extend common operations there (there is not any refactor there) ## How was this patch tested? FT: manually This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24914) Block Ozone datanode co-location with HDFS Datanode when added though the API
Dmytro Sen created AMBARI-24914: --- Summary: Block Ozone datanode co-location with HDFS Datanode when added though the API Key: AMBARI-24914 URL: https://issues.apache.org/jira/browse/AMBARI-24914 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 * Do not allow user to call and API that add Ozone datanode to a host with HDFS datanode * Converse also holds * Make sure this is a flag at stack level and blueprints also follow the same validation rule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24913) Update ldap-configuration category in Ambari Configurations data to contain properties to aid in automated LDAP configuration
Sandor Molnar created AMBARI-24913:
--
Summary: Update ldap-configuration category in Ambari
Configurations data to contain properties to aid in automated LDAP configuration
Key: AMBARI-24913
URL: https://issues.apache.org/jira/browse/AMBARI-24913
Project: Ambari
Issue Type: Task
Components: ambari-server, security
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.8.0
Update {{ldap-configuration}} category in Ambari Configurations data to contain
properties to aid in automated LDAP configuration:
* {{ambari.ldap.manage_services}}
** This property is used to indicate whether Ambari is to manage relevant
services' LDAP configurations or not ("true" | "false")
* {{ambari.ldap.enabled_services}}
** This property is used to declare what services are expected to be
configured for LDAP and is expected to be a comma-delimited list of services or
"{{*}}" to indicate all services.
Examples:
{code:java|title=All services}
"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"*"
{code}
{code:java|title=Only Ranger}
"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"Ranger"
{code}
{code:java|title=Ranger, and Atlas}
"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"Ranger, Atlas"
{code}
{code:java|title=Do not manage services}
"ambari.ldap.manage_services":"false",
"ambari.ldap.enabled_services":""
{code}
Each service in the set of services should have indicated it supports LDAP (see
BUG-114409) else it will silently be ignored.
This value should be set via Ambari's REST API or a Blueprint.
Upon setting this value via the Ambari REST API, it is expected that internal
logic will be triggered to ensure the relevant services in the list are
configured for LDAP or not configured for LDAP as the case may be.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689280#comment-16689280 ] Hudson commented on AMBARI-24833: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #34 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/34/]) AMBARI-24833. Extend cloud log rolling options (#25) (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=31c70d37c30488205d91f666316949d9a7242dd8]) * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CloudStorageUploader.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/UploadClientFactory.java * (edit) ambari-logsearch-logfeeder/pom.xml * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/CloudStorageDestination.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/HDFSUploadClient.java * (edit) ambari-logsearch-logfeeder/src/main/resources/logfeeder.properties * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/CloudStorageLoggerFactory.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/ExternalHdfsOutputConfig.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/cloud/upload/ExternalHDFSUploadClient.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java * (edit) ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/RolloverConfig.java > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[
https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689276#comment-16689276
]
ASF GitHub Bot commented on AMBARI-24833:
-
oleewere closed pull request #25: AMBARI-24833. Extend cloud log rolling options
URL: https://github.com/apache/ambari-logsearch/pull/25
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-logsearch-logfeeder/pom.xml
b/ambari-logsearch-logfeeder/pom.xml
index e71b3cc555..003b23357f 100644
--- a/ambari-logsearch-logfeeder/pom.xml
+++ b/ambari-logsearch-logfeeder/pom.xml
@@ -150,6 +150,12 @@
org.apache.hadoop
hadoop-aws
${hadoop.version}
+
+
+ com.amazonaws
+ aws-java-sdk-bundle
+
+
com.amazonaws
@@ -161,6 +167,11 @@
aws-java-sdk-s3
${aws-sdk.version}
+
+ com.amazonaws
+ aws-java-sdk-dynamodb
+ ${aws-sdk.version}
+
org.apache.hadoop
hadoop-azure
diff --git
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
index 11d351f23d..b5fffa829b 100644
---
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
+++
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java
@@ -34,10 +34,6 @@
// Event History Constants History
public static final String VALUES = "jsons";
public static final String ROW_TYPE = "rowtype";
-
- // S3 Constants
- public static final String S3_PATH_START_WITH = "s3://";
- public static final String S3_PATH_SEPARATOR = "/";
public static final String IN_MEMORY_TIMESTAMP = "in_memory_timestamp";
@@ -122,14 +118,17 @@
public static final String CLOUD_ROLLOVER_ARCHIVE_LOCATION =
"logfeeder.cloud.rollover.archive.base.dir";
public static final String CLOUD_ROLLOVER_THRESHOLD_TIME_MIN =
"logfeeder.cloud.rollover.threshold.min";
public static final String CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE =
"logfeeder.cloud.rollover.threshold.size";
+ public static final String CLOUD_ROLLOVER_MAX_BACKUP_FILES =
"logfeeder.cloud.rollover.max.files";
+ public static final String CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE_UNIT =
"logfeeder.cloud.rollover.threshold.size.unit";
public static final String CLOUD_ROLLOVER_USE_GZIP =
"logfeeder.cloud.rollover.use.gzip";
public static final String CLOUD_ROLLOVER_IMMEDIATE_FLUSH =
"logfeeder.cloud.rollover.immediate.flush";
public static final String CLOUD_ROLLOVER_ON_SHUTDOWN =
"logfeeder.cloud.rollover.on.shutdown";
public static final String CLOUD_ROLLOVER_ON_STARTUP =
"logfeeder.cloud.rollover.on.startup";
+ public static final String HDFS_USER = "logfeeder.hdfs.user";
+
public static final String HDFS_HOST = "logfeeder.hdfs.host";
public static final String HDFS_PORT = "logfeeder.hdfs.port";
- public static final String HDFS_USER = "logfeeder.hdfs.user";
public static final String HDFS_FILE_PERMISSIONS =
"logfeeder.hdfs.file.permissions";
public static final String HDFS_KERBEROS = "logfeeder.hdfs.kerberos";
diff --git
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/CloudStorageDestination.java
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/CloudStorageDestination.java
index 1a7eafa509..0246b98306 100644
---
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/CloudStorageDestination.java
+++
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/CloudStorageDestination.java
@@ -19,7 +19,7 @@
package org.apache.ambari.logfeeder.conf;
public enum CloudStorageDestination {
- HDFS("hdfs"), S3("s3"), GCS("gcs"), ADLS("adls"), NONE("none");
+ HDFS("hdfs"), S3("s3"), GCS("gcs"), ADLS("adls"), WASB("wasb"),
DEFAULT_FS("default-fs"), NONE("none");
private String text;
diff --git
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
index d32e1df9db..83f10e497c 100644
---
a/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
+++
b/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
@@ -224,7 +224,8 @@
@LogSearchPropertyDescription(
name = LogFeederConstants.CLOUD_STORAGE_DESTINATION,
description = "Type of storage that is the destination for cloud output
logs.",
-examples = {"hdfs", "s3",
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689274#comment-16689274 ] ASF GitHub Bot commented on AMBARI-24833: - asfgit commented on issue #25: AMBARI-24833. Extend cloud log rolling options URL: https://github.com/apache/ambari-logsearch/pull/25#issuecomment-439354665 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/52/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24871) Create an Ambari-server class that is called as an entry point to encrypt service configuration sensitive data
[ https://issues.apache.org/jira/browse/AMBARI-24871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-24871. - Resolution: Fixed > Create an Ambari-server class that is called as an entry point to encrypt > service configuration sensitive data > -- > > Key: AMBARI-24871 > URL: https://issues.apache.org/jira/browse/AMBARI-24871 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 5h > Remaining Estimate: 0h > > Create a java class that is called as an entry point to encrypt service > configuration sensitive data. This script will be called from a python script > just like it is done for pre-checks, or for upgrade catalogs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24912) Infra Manager: scheduled job fails with dateparse exception
[ https://issues.apache.org/jira/browse/AMBARI-24912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689242#comment-16689242 ] ASF GitHub Bot commented on AMBARI-24912: - asfgit commented on issue #16: AMBARI-24912 - Infra Manager: scheduled job fails with dateparse exception URL: https://github.com/apache/ambari-infra/pull/16#issuecomment-439343977 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-Infra-Github-PR-Builder/24/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: scheduled job fails with dateparse exception > --- > > Key: AMBARI-24912 > URL: https://issues.apache.org/jira/browse/AMBARI-24912 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24912) Infra Manager: scheduled job fails with dateparse exception
[ https://issues.apache.org/jira/browse/AMBARI-24912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24912: Labels: pull-request-available (was: ) > Infra Manager: scheduled job fails with dateparse exception > --- > > Key: AMBARI-24912 > URL: https://issues.apache.org/jira/browse/AMBARI-24912 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[
https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689253#comment-16689253
]
ASF GitHub Bot commented on AMBARI-24833:
-
kasakrisz commented on a change in pull request #25: AMBARI-24833. Extend cloud
log rolling options
URL: https://github.com/apache/ambari-logsearch/pull/25#discussion_r234152011
##
File path:
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/output/RolloverConfig.java
##
@@ -49,12 +49,32 @@
@LogSearchPropertyDescription(
name = LogFeederConstants.CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE,
description = "Rollover cloud log files after the log file size reach this
limit",
-examples = {"1024KB"},
-defaultValue = "80MB",
+examples = {"1024"},
+defaultValue = "80",
sources = {LogFeederConstants.LOGFEEDER_PROPERTIES_FILE}
)
- @Value("${"+ LogFeederConstants.CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE +
":80MB}")
- private String rolloverSize;
+ @Value("${"+ LogFeederConstants.CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE + ":80}")
+ private Integer rolloverSize;
+
+ @LogSearchPropertyDescription(
+name = LogFeederConstants.CLOUD_ROLLOVER_MAX_BACKUP_FILES,
+description = "The number of max backup log files for rolled over logs.",
+examples = {"50"},
+defaultValue = "10",
+sources = {LogFeederConstants.LOGFEEDER_PROPERTIES_FILE}
+ )
+ @Value("${"+ LogFeederConstants.CLOUD_ROLLOVER_MAX_BACKUP_FILES + ":10}")
+ private Integer rolloverMaxBackupFiles;
+
+ @LogSearchPropertyDescription(
+name = LogFeederConstants.CLOUD_ROLLOVER_THRESHOLD_TIME_SIZE_FORMAT,
+description = "Rollover cloud log file size format (e.g: KB, MB etc.)",
Review comment:
Unit or format?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Log Feeder: send logs to cloud storage (gcs/s3 etc.)
>
>
> Key: AMBARI-24833
> URL: https://issues.apache.org/jira/browse/AMBARI-24833
> 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.8.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[
https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689254#comment-16689254
]
ASF GitHub Bot commented on AMBARI-24833:
-
kasakrisz commented on a change in pull request #25: AMBARI-24833. Extend cloud
log rolling options
URL: https://github.com/apache/ambari-logsearch/pull/25#discussion_r234151152
##
File path:
ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java
##
@@ -224,7 +224,8 @@
@LogSearchPropertyDescription(
name = LogFeederConstants.CLOUD_STORAGE_DESTINATION,
description = "Type of storage that is the destination for cloud output
logs.",
-examples = {"hdfs", "s3", "gcs", "adls", "none"},
+examples = {"hdfs", "s3", "gcs", "adls", "wasb", "none"},
Review comment:
Can `default-fs` be set here?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Log Feeder: send logs to cloud storage (gcs/s3 etc.)
>
>
> Key: AMBARI-24833
> URL: https://issues.apache.org/jira/browse/AMBARI-24833
> 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.8.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24833) Log Feeder: send logs to cloud storage (gcs/s3 etc.)
[ https://issues.apache.org/jira/browse/AMBARI-24833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689236#comment-16689236 ] ASF GitHub Bot commented on AMBARI-24833: - asfgit commented on issue #25: AMBARI-24833. Extend cloud log rolling options URL: https://github.com/apache/ambari-logsearch/pull/25#issuecomment-439342879 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/Ambari-LogSearch-Github-PR-Builder/51/ Test PASSed. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Log Feeder: send logs to cloud storage (gcs/s3 etc.) > > > Key: AMBARI-24833 > URL: https://issues.apache.org/jira/browse/AMBARI-24833 > 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.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24912) Infra Manager: scheduled job fails with dateparse exception
[ https://issues.apache.org/jira/browse/AMBARI-24912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24912: Status: Patch Available (was: Open) > Infra Manager: scheduled job fails with dateparse exception > --- > > Key: AMBARI-24912 > URL: https://issues.apache.org/jira/browse/AMBARI-24912 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24879) The kadmin service principal name should be configurable for MIT KDC interactions
[
https://issues.apache.org/jira/browse/AMBARI-24879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar resolved AMBARI-24879.
Resolution: Fixed
> The kadmin service principal name should be configurable for MIT KDC
> interactions
> -
>
> Key: AMBARI-24879
> URL: https://issues.apache.org/jira/browse/AMBARI-24879
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The kadmin service principal name should be configurable for MIT KDC
> interactions. The current process assumes the kadmin service principal is
> {{kadmin/FQDN_KADMIN_HOST}}, but this could be different on some
> installations. For example, {{kadmin/admin}}.
> A new kerberos-env property should be added to allow a user to change the
> kadmin principal name - {{kerberos-env/kadmin_principal_name}}
> The default value for the new property should be
> "{{kadmin/$\{admin_server_host|stripPort()}}}". To be able to do this, we
> have to create a new variable replacement _function_. For example,
> {{stripPort}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24912) Infra Manager: scheduled job fails with dateparse exception
[ https://issues.apache.org/jira/browse/AMBARI-24912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689241#comment-16689241 ] ASF GitHub Bot commented on AMBARI-24912: - kasakrisz opened a new pull request #16: AMBARI-24912 - Infra Manager: scheduled job fails with dateparse exception URL: https://github.com/apache/ambari-infra/pull/16 ## What changes were proposed in this pull request? Use UTC time zone when a scheduled archiving job launched to calculate the end of interval of archivable document from system time ## How was this patch tested? UTs ITs passed Manually: 1. Deploy ambari and a cluster: zookeeper, infra-solr, infra-manager, logsearch 2. Schedule an archiving job like archive_service_logs 3. wait until its first run 4. check for archived documents This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: scheduled job fails with dateparse exception > --- > > Key: AMBARI-24912 > URL: https://issues.apache.org/jira/browse/AMBARI-24912 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.8.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689211#comment-16689211 ] Hudson commented on AMBARI-24891: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #32 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/32/]) [AMBARI-24891] [Log Serach UI] The Log Index Filter panel does not work (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=02ae3ad0ee9df1e82a08f336b565fa826a3d16e8]) * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.html * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-list/dropdown-list.component.ts * (edit) ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts * (edit) ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html * (edit) ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/filter-dropdown/filter-dropdown.component.ts * (edit) ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts * (edit) ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts > [Log Serach UI] The Log Index Filter panel does not work > > > Key: AMBARI-24891 > URL: https://issues.apache.org/jira/browse/AMBARI-24891 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > > The Log Index Filter settings modal does not load the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689216#comment-16689216 ] Hudson commented on AMBARI-24899: - SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #33 (See [https://builds.apache.org/job/Ambari-LogSearch-master-Commit/33/]) [AMBARI-24899] [Log Search UI] Change capture countdown text (#24) (github: [https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git=commit=fbfc907e2039087879c40439d25623353466f583]) * (edit) ambari-logsearch-web/src/assets/i18n/en.json > [Log Search UI] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24899) [Log Search UI] Change capture countdown text
[
https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689207#comment-16689207
]
ASF GitHub Bot commented on AMBARI-24899:
-
tobias-istvan closed pull request #24: [AMBARI-24899] [Log Search UI] Change
capture countdown text
URL: https://github.com/apache/ambari-logsearch/pull/24
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-logsearch-web/src/assets/i18n/en.json
b/ambari-logsearch-web/src/assets/i18n/en.json
index 770f5e9dfe..0e60563e15 100644
--- a/ambari-logsearch-web/src/assets/i18n/en.json
+++ b/ambari-logsearch-web/src/assets/i18n/en.json
@@ -55,7 +55,7 @@
"filter.capture": "Capture",
"filter.captureSnapshot": "Snapshot",
- "filter.refreshingLogListIn": "Refreshing log list in...",
+ "filter.refreshingLogListIn": "Please wait while the logs for your capture
period are indexed...",
"filter.capture.min": "Min",
"filter.capture.sec": "Sec",
"filter.capture.triggeringRefresh": "Triggering auto-refresh in
{{remainingSeconds}} sec",
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Log Search UI] Change capture countdown text
> -
>
> Key: AMBARI-24899
> URL: https://issues.apache.org/jira/browse/AMBARI-24899
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch, logsearch
>Affects Versions: 2.7.3
>Reporter: Istvan Tobias
>Assignee: Istvan Tobias
>Priority: Trivial
> Labels: pull-request-available
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The text should be: "Please wait while the logs for your capture period are
> indexed..."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24899) [Log Search UI] Change capture countdown text
[ https://issues.apache.org/jira/browse/AMBARI-24899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24899: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Search UI] Change capture countdown text > - > > Key: AMBARI-24899 > URL: https://issues.apache.org/jira/browse/AMBARI-24899 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Trivial > Labels: pull-request-available > Original Estimate: 1h > Remaining Estimate: 1h > > The text should be: "Please wait while the logs for your capture period are > indexed..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[ https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24891: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Log Serach UI] The Log Index Filter panel does not work > > > Key: AMBARI-24891 > URL: https://issues.apache.org/jira/browse/AMBARI-24891 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.3 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > > The Log Index Filter settings modal does not load the configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24891) [Log Serach UI] The Log Index Filter panel does not work
[
https://issues.apache.org/jira/browse/AMBARI-24891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689205#comment-16689205
]
ASF GitHub Bot commented on AMBARI-24891:
-
tobias-istvan closed pull request #23: [AMBARI-24891] [Log Serach UI] The Log
Index Filter panel does not work
URL: https://github.com/apache/ambari-logsearch/pull/23
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
index 721ae93d74..a5d9ae2f32 100644
---
a/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
+++
b/ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
@@ -75,6 +75,9 @@ export class ActionMenuComponent implements OnInit,
OnDestroy {
this.selectedClusterName$.takeUntil(this.destroyed$).subscribe(
(clusterName: string) => this.setModalSubmitDisabled(!clusterName)
);
+this.clustersListItems$.filter((items: ListItem[]) => items.some((item:
ListItem) => item.isChecked)).first()
+ .map((items: ListItem[]) => items.find((item: ListItem) =>
item.isChecked))
+ .subscribe((item) => this.selectedClusterName$.next(item.value));
}
ngOnDestroy() {
diff --git
a/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts
b/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts
index d6f24e5291..21cc1510f2 100644
---
a/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts
+++
b/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts
@@ -51,7 +51,7 @@ export class FilterButtonComponent extends
MenuButtonComponent implements Contro
}
writeValue(items: ListItem[]) {
-this.selection = items;
+this.selection = items ? (Array.isArray(items) ? items : [items] ) : [];
}
registerOnChange(callback: any): void {
diff --git
a/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html
b/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html
index 7061defaa7..28cde2be3f 100644
---
a/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html
+++
b/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.html
@@ -15,7 +15,7 @@
limitations under the License.
-->
-
+
diff --git
a/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts
b/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts
index faf2165c7a..317499146f 100644
---
a/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts
+++
b/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts
@@ -127,6 +127,14 @@ export class MenuButtonComponent {
return this.subItems && this.subItems.filter((option: ListItem): boolean
=> option.isChecked);
}
+ get hasSelection(): boolean {
+return this.subItems && this.subItems.filter((option: ListItem): boolean
=> option.isChecked).length > 0;
+ }
+
+ get totalSelection(): number {
+return this.subItems ? this.subItems.filter((option: ListItem): boolean =>
option.isChecked).length : 0;
+ }
+
constructor(private utils: UtilsService) {}
findItemIndexInList(item: ListItem, itemList: ListItem[] = this.subItems):
number {
diff --git
a/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.html
b/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.html
index 714002854a..f4fdf4f1b6 100644
---
a/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.html
+++
b/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.html
@@ -15,17 +15,19 @@
limitations under the License.
-->
-
+
-
{{label}}
- {{selection[0].label |
translate}}
+
+{{ item.label | translate }}
+
diff --git
a/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts
b/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts
index 74341aeff4..2d04f210e5 100644
---
a/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts
+++
b/ambari-logsearch-web/src/app/modules/shared/components/dropdown-button/dropdown-button.component.ts
@@ -67,14 +67,31 @@ export class DropdownButtonComponent {
@Input()
[jira] [Commented] (AMBARI-24907) Update service metainfo to declare LDAP integration support
[
https://issues.apache.org/jira/browse/AMBARI-24907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689194#comment-16689194
]
Hudson commented on AMBARI-24907:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10302 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10302/])
AMBARI-24907. Updated service metainfo to declare LDAP integration (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=9419944925f3b210ce429ba147e1462478259261])
* (add)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceLdapInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AddServiceRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ServiceResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceResponse.java
> Update service metainfo to declare LDAP integration support
> ---
>
> Key: AMBARI-24907
> URL: https://issues.apache.org/jira/browse/AMBARI-24907
> Project: Ambari
> Issue Type: Task
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Update service metainfo to declare LDAP integration support. The following
> tag may be optionally set in a service's metainfo.xml file:
> {noformat}
>
> true
>
> {
> "equals": [
> "ranger-admin-site/ranger.authentication.method",
> "LDAP"
> ]
> }
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24912) Infra Manager: scheduled job fails with dateparse exception
Krisztian Kasa created AMBARI-24912: --- Summary: Infra Manager: scheduled job fails with dateparse exception Key: AMBARI-24912 URL: https://issues.apache.org/jira/browse/AMBARI-24912 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.8.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
