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

Ricky Saltzer commented on NIFI-1629:
-------------------------------------

+1 - tested this with 2 consumers, one 0.8.0 and one 0.9.0. 

{code}
Standard FlowFile Attributes
Key: 'entryDate'
        Value: 'Wed Mar 16 15:29:35 EDT 2016'
Key: 'lineageStartDate'
        Value: 'Wed Mar 16 15:29:35 EDT 2016'
Key: 'fileSize'
        Value: '24'
FlowFile Attribute Map Content
Key: 'filename'
        Value: '98204303298785'
Key: 'kafka.offset'
        Value: '2'
Key: 'kafka.partition'
        Value: '0'
Key: 'kafka.topic'
        Value: 'test-topic'
Key: 'path'
        Value: './'
Key: 'uuid'
        Value: 'd02d00d6-dfff-4273-9478-a8e10f84b1c8'
--------------------------------------------------
test-message-kafka-0.8.0

--------------------------------------------------
Standard FlowFile Attributes
Key: 'entryDate'
        Value: 'Wed Mar 16 15:29:36 EDT 2016'
Key: 'lineageStartDate'
        Value: 'Wed Mar 16 15:29:36 EDT 2016'
Key: 'fileSize'
        Value: '24'
FlowFile Attribute Map Content
Key: 'filename'
        Value: '98205812457936'
Key: 'kafka.offset'
        Value: '1'
Key: 'kafka.partition'
        Value: '0'
Key: 'kafka.topic'
        Value: 'test-topic'
Key: 'path'
        Value: './'
Key: 'uuid'
        Value: 'a72f906d-ee0f-495d-8f10-5953411d0ce6'
--------------------------------------------------
test-message-kafka-0.9.0
{code}

> Downgrade Kafka processors back to 0.8
> --------------------------------------
>
>                 Key: NIFI-1629
>                 URL: https://issues.apache.org/jira/browse/NIFI-1629
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>             Fix For: 0.6.0
>
>
> Also, the following needs to be added to ensure that Kafka failures do not 
> affect NiFi operations
> 1) Add yield so when we don't have to ack anything or there is nothing to 
> send we don't do onTrigger()
> 2) Appropriate hooks allowing Kafka processors to still exit whenever Kafka 
> deadlocks



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

Reply via email to