[
https://issues.apache.org/jira/browse/METRON-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957808#comment-15957808
]
ASF GitHub Bot commented on METRON-623:
---------------------------------------
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/489#discussion_r110036136
--- 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 --
We have a '/api/v1/hdfs/{path}" endpoint that returns hdfs file contents.
That's the first call the client side makes. If that fails, it calls
'/api/v1/grok/get/statement' to get the pattern from the classpath. If that
fails it reports an error in the UI.
We could change '/api/v1/grok/get/statement' to check HDFS first and change
the client side logic to only call the grok endpoint. Does that make more
sense to you and do you think it's worth making that change?
> 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)
