[
https://issues.apache.org/jira/browse/METRON-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628179#comment-16628179
]
ASF GitHub Bot commented on METRON-1787:
----------------------------------------
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/1209#discussion_r220410471
--- Diff:
metron-analytics/metron-profiler-spark/src/main/java/org/apache/metron/profiler/spark/function/MessageRouterFunction.java
---
@@ -80,19 +100,54 @@ public MessageRouterFunction(ProfilerConfig
profilerConfig, Map<String, String>
Optional<JSONObject> message = toMessage(jsonMessage, parser);
if(message.isPresent()) {
- // find all routes
- routes = router.route(message.get(), profilerConfig, context);
- LOG.trace("Found {} route(s) for a message", routes.size());
+ // extract the timestamp from the message
+ Clock clock = clockFactory.createClock(profilerConfig);
--- End diff --
See comments in the clock factory class regarding cached instance.
> Input Time Constraints for Batch Profiler
> -----------------------------------------
>
> Key: METRON-1787
> URL: https://issues.apache.org/jira/browse/METRON-1787
> Project: Metron
> Issue Type: Sub-task
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> A user should be able to constrain the input telemetry based on time. The
> user might optionally provide a --begin and/or --end command line argument
> that defines the time window.
>
> This was originally [discussed on the mailing
> list|https://lists.apache.org/thread.html/39b5636c9ae264611aa8aecc426b649682efaf1bd0755848a90ee6b9@%3Cdev.metron.apache.org%3E].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
