You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2016/10/03 14:42:20 UTC

[jira] [Updated] (NIFI-2826) GetEventHubProcessor Support Enqueue Time

     [ https://issues.apache.org/jira/browse/NIFI-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Percivall updated NIFI-2826:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Resolved with this commit: https://github.com/apache/nifi/commit/34e5a5321ab5e5d02e22932f115be982b3b5b304

> 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)