[
https://issues.apache.org/jira/browse/METRON-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951264#comment-15951264
]
ASF GitHub Bot commented on METRON-623:
---------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/489#discussion_r109203096
--- Diff:
metron-interface/metron-rest/src/main/java/org/apache/metron/rest/controller/GrokController.java
---
@@ -53,4 +54,11 @@
ResponseEntity<Map<String, String>> list() throws RestException {
return new ResponseEntity<>(grokService.getCommonGrokPatterns(),
HttpStatus.OK);
}
+
+ @ApiOperation(value = "Retrieves a Grok statement from the classpath")
+ @ApiResponse(message = "Grok statement", code = 200)
+ @RequestMapping(value = "/get/statement", method = RequestMethod.GET)
--- End diff --
Sorry, maybe I'm not groking (ha) exactly how this call is used. When
would we ever want a REST call that wouldn't fall back to HDFS?
> Management UI
> -------------
>
> Key: METRON-623
> URL: https://issues.apache.org/jira/browse/METRON-623
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
>
> It would be useful to have a User Interface for modifying parser/enrichment
> configurations and managing topologies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
