[jira] [Reopened] (AMBARI-20578) Log Search Configuration API

["Doroszlai, Attila (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-20578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doroszlai, Attila reopened AMBARI-20578:
----------------------------------------

[~mgergely], could you please check the [NPE in UpgradeCatalog300Test|https://builds.apache.org/job/Ambari-trunk-Commit/7276/testReport/junit/org.apache.ambari.server.upgrade/UpgradeCatalog300Test/testExecuteDMLUpdates/] introduced in this commit?

{noformat}
testExecuteDMLUpdates(org.apache.ambari.server.upgrade.UpgradeCatalog300Test)  Time elapsed: 0.052 sec  <<< ERROR!
java.lang.NullPointerException
	at org.apache.ambari.server.upgrade.UpgradeCatalog300Test.testExecuteDMLUpdates(UpgradeCatalog300Test.java:149)
{noformat}

> Log Search Configuration API
> ----------------------------
>
>                 Key: AMBARI-20578
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20578
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 3.0.0
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>             Fix For: 3.0.0
>
>
> Log Search should store it's configurations (inputs, filters) by using an API, which the user may implement as well to use their own way of storing the configurations. By default for now we offer to store everything in ZooKeeper.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)