[
https://issues.apache.org/jira/browse/METRON-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564019#comment-16564019
]
ASF GitHub Bot commented on METRON-1700:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/1135#discussion_r206605219
--- Diff: metron-interface/metron-rest/README.md ---
@@ -556,6 +558,14 @@ Request and Response objects are JSON formatted. The
JSON schemas are available
* jobId - Job ID of submitted job
* Returns:
* 200 - Kills passed job.
+
+### `GET /api/v1/pcap/{jobId}/configuration`
--- End diff --
Small nit: In the existing endpoints, we have tended to use "config"
instead of "configuration". Would it make sense to use "config" here for
consistency?
> Create REST endpoint to get job configuration
> ---------------------------------------------
>
> Key: METRON-1700
> URL: https://issues.apache.org/jira/browse/METRON-1700
> Project: Metron
> Issue Type: Sub-task
> Reporter: Ryan Merriman
> Priority: Major
>
> We need a REST endpoint that will allow us to retrieve the job configuration
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
