[
https://issues.apache.org/jira/browse/AMBARI-25012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712844#comment-16712844
]
Hudson commented on AMBARI-25012:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-LogSearch-master-Commit #73 (See
[https://builds.apache.org/job/Ambari-LogSearch-master-Commit/73/])
[AMBARI-25012] Log Search UI: cannot save filters + select all selecting
(github:
[https://gitbox.apache.org/repos/asf?p=ambari-logsearch.git&a=commit&h=b21991615d744a983799af24631d64c4d0640e5c])
* (edit)
ambari-logsearch-web/src/app/components/action-menu/action-menu.component.html
* (edit)
ambari-logsearch-web/src/app/components/action-menu/action-menu.component.ts
* (edit)
ambari-logsearch-web/src/app/components/log-index-filter/log-index-filter.component.ts
> Log Search UI: cannot save filters + select all selecting the ovirrides as
> well
> -------------------------------------------------------------------------------
>
> Key: AMBARI-25012
> URL: https://issues.apache.org/jira/browse/AMBARI-25012
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch, logsearch
> Affects Versions: 2.7.3
> Reporter: Istvan Tobias
> Assignee: Istvan Tobias
> Priority: Blocker
> Labels: pull-request-available
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Clicking out a log level from debug to nothing, save button was still
> disabled.
> Also clicking select all selected the overrides rows as well (as no hostname
> set there or anything, not sure what is expected there, hopefully we would
> not save that with filled empty hostname but with one debug log level)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
