[
https://issues.apache.org/jira/browse/METRON-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554233#comment-16554233
]
ASF GitHub Bot commented on METRON-1671:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1103
@mmiklavc The job manager is asynchronous in that it accepts a Finalizer.
We have the polling loop in place but we would need to refactor the job manager
to expose a callback function for getStatus.
@justinleet I get where you're coming from, async communication would be
ideal. For this use case though, I don't see much of a benefit. There is no
reason we can't send status for all user jobs in response to a single polling
request (a trivial change since there is already a getJobs method on the job
manager). Also, we are reporting percentage done so there would likely be
multiple aysnc calls anyways as the job progresses.
This is definitely something we should add to our platform and I would be
happy to work on it with you. Sounds like you're ok with this being a follow
on. I'm sure we'll need this construct at some point in the near future.
> Create PCAP UI
> --------------
>
> Key: METRON-1671
> URL: https://issues.apache.org/jira/browse/METRON-1671
> Project: Metron
> Issue Type: Sub-task
> Reporter: Tibor Meller
> Priority: Major
>
> The initial feature set of PCAP UI is the follwing:
> - Filtering by
> - IP Source Address
> - IP Source Port
> - IP Dest Address
> - IP Dest Port
> - Protocol
> - Include Reverse Traffic
> - Free text filtering
> - Showing PDML result
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
