[ https://issues.apache.org/jira/browse/STORM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310217#comment-14310217 ]
ASF GitHub Bot commented on STORM-659: -------------------------------------- GitHub user d2r opened a pull request: https://github.com/apache/storm/pull/420 [STORM-659] return grep matches each on its own line You can merge this pull request into a Git repository by running: $ git pull https://github.com/d2r/storm storm-659-grep-match-lines Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/420.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #420 ---- commit 4f468d91494811f22f82154698317e7ed7cabf29 Author: Derek Dagit <der...@yahoo-inc.com> Date: 2015-02-06T23:47:06Z return grep matches each on its own line ---- > Logviewer used with grep param returns all matches on one line > -------------------------------------------------------------- > > Key: STORM-659 > URL: https://issues.apache.org/jira/browse/STORM-659 > Project: Apache Storm > Issue Type: Bug > Affects Versions: 0.9.3 > Reporter: Derek Dagit > Assignee: Derek Dagit > Priority: Minor > > Adding the grep=searchstring parameter to the logviewer URL will search the > log file for lines with the string in it. But it then returns all matches on > one line within a preformatted text block. It should return matches each on > its own line so that it is easier to read. -- This message was sent by Atlassian JIRA (v6.3.4#6332)