[
https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542565#comment-15542565
]
Joseph Percivall commented on NIFI-2826:
----------------------------------------
Hey [~josephxsxn] you had a couple check style issues (revealed by running "mvn
clean install -Pcontrib-check") but I fixed them and amended your commit.
+1
Visually verified code and did a contrib check build (passed after my fix was
added). In a standealone instance, tested using Azure Event hub and IoT hub.
Properly saw data come in as it was produced and also saw historical data come
in when the enqueue time was set. Thanks for the contribution Joe! I look
forward to reviewing more of your commits in the future. I will merge it in.
> GetEventHubProcessor Support Enqueue Time
> -----------------------------------------
>
> Key: NIFI-2826
> URL: https://issues.apache.org/jira/browse/NIFI-2826
> Project: Apache NiFi
> Issue Type: Improvement
> Environment: centos6, jdk1.8, nifi 1.0.0
> Reporter: Joseph Niemiec
> Assignee: Joseph Niemiec
> Priority: Minor
> Fix For: 1.1.0
>
> Attachments:
> 0001-NIFI-2826-Adding-enqueue-time-to-GetAzureEventHub-pr.patch,
> 0002-NIFI-2826-converted-from-epoch-to-iso8061-enqueue-in.patch,
> 0003-NIFI-2826-Adding-enqueue-time-to-GetAzureEventHub-pr.patch, patch.1
>
>
> The current GetEventHubProcessor should support allowing an enqueue time like
> eventhubs to read messages from the past. This would also support reading
> messages missed during downtime. Today the behaviour is for the processor to
> start at the enqueue of when it was started by the user missing any past
> messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
