You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Zhengdai Hu (JIRA)" <ji...@apache.org> on 2018/08/10 21:17:00 UTC
[jira] [Created] (STORM-3193) Improve LogviewerLogSearchHandler
Zhengdai Hu created STORM-3193:
----------------------------------
Summary: Improve LogviewerLogSearchHandler
Key: STORM-3193
URL: https://issues.apache.org/jira/browse/STORM-3193
Project: Apache Storm
Issue Type: Improvement
Reporter: Zhengdai Hu
One thing that is worthy of noticing: Storm UI currently interweaves different search API regarding searching functionalities and it's kind of confusing.
Specifically:
For the search button at homepage, it uses a single deep search API to search all ports (server side process), both archived and non-archived.
For non-archived search at a specific topology page, it invokes search API on each port inside a loop (client side process).
For archived search at a specific topology page, it invokes deep search API (search-archived=on) on each port inside a loop (client side process)
As a result, metrics for these APIs may not accurately reflect how many searches are invoked from client's perspective.
Additionally, `findNMatches` can be simplified, along with STORM-3189
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)