[
https://issues.apache.org/jira/browse/METRON-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628762#comment-16628762
]
ASF GitHub Bot commented on METRON-1787:
----------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/metron/pull/1209#discussion_r220557437
--- Diff: metron-analytics/metron-profiler-spark/README.md ---
@@ -263,6 +265,18 @@ The path to the input data read by the Batch Profiler.
The format of the input data read by the Batch Profiler.
+### `profiler.batch.input.begin`
+
+*Default*: undefined
+
+Only messages with a timestamp after this will be profiled. By default, no
time constraint is defined. The value is expected to follow the [ISO-8601
instant
format](https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_INSTANT);
2011-12-03T10:15:30Z.
+
+### `profiler.batch.input.end`
--- End diff --
I updated the README to clarify this point.
> 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)
