You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2015/11/25 17:21:10 UTC

[jira] [Commented] (NIFI-1219) Add support for controlling the topic offset from which to pull Kafka events from

    [ https://issues.apache.org/jira/browse/NIFI-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027025#comment-15027025 ] 

Oleg Zhurakousky commented on NIFI-1219:
----------------------------------------

Actually may have pulled the trigger too soon. [~markap14] just pointed out that it has been already addressed 
{code}
 public static final PropertyDescriptor AUTO_OFFSET_RESET = new PropertyDescriptor.Builder()
            .name("Auto Offset Reset")
            .description("Automatically reset the offset to the smallest or largest offset available on the broker")
            .required(true)
            .allowableValues(SMALLEST, LARGEST)
            .defaultValue(LARGEST)
            .build();
{code}
Will rename the issue to only add embedded Kafka for testing (minor)


> Add support for controlling the topic offset from which to pull Kafka events from
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-1219
>                 URL: https://issues.apache.org/jira/browse/NIFI-1219
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.3.0
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>             Fix For: 0.5.0
>
>
> While still investigating, it's becoming very clear that at the moment GetKafka only pulls events that are current after consumer is initialized. In other words events that were put on the topic before are not pulled.
> I am also working in assembling a stable embedded version of Kafka that will help with testing this feature along as current functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)