[
https://issues.apache.org/jira/browse/METRON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525244#comment-16525244
]
ASF GitHub Bot commented on METRON-1641:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1081
I think for a first cut, it's ok to have the restrictions that:
* the REST API controls only the jobs it creates. Otherwise, we would need
more refactoring in the CLI to drop the output in the same HDFS directory
rather than it be user specifiable and output locally. Ultimately, while they
use the same mechanism, the UX is different between the two approaches (e.g.
the CLI entirely cleans up after itself and outputs to the local directory
whereas the REST approach stores the results in HDFS until manual cleanup).
* If a job is running while the REST API dies, we should consider that job
to be runaway and needs to be killed by the admin or left to complete without
the result being published. One thing that we might consider doing is enabling
the job naming to have a prefix of `METRON_REST_PCAP` so, upon REST start, it
can kill existing jobs. I think for THIS PR, we should just have REST pcap
jobs have that prefix and leave it to a follow-on PR to do the actual killing.
> Enable Pcap jobs to be submitted asynchronously
> -----------------------------------------------
>
> Key: METRON-1641
> URL: https://issues.apache.org/jira/browse/METRON-1641
> Project: Metron
> Issue Type: New Feature
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
