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

Adam Hunyadi updated MINIFICPP-1373:
------------------------------------
    Description: 
*Acceptance Criteria:*

*{color:#de350b}See attached test matrix plan.{color}*

Additional test (that require multiple Kafka consumers):
h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with 
{color:#0747a6}different group ids{color} subscribed to the same topic
 {color:#505f79}*WHEN*{color} a message is published to the topic
 {color:#505f79}*THEN*{color} both of the ConsumeKafka processors should 
produce identical flowfiles
h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
same group id{color} subscribed to the same topic
{color:#505f79}*WHEN*{color} a message is published to the topic
{color:#505f79}*THEN*{color} both of the ConsumeKafka processors should produce 
identical flowfiles
h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
same group id{color} subscribed to the same topic with exactly two partitions 
with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}earliest{color}.
{color:#505f79}*WHEN*{color} a messages were already present on both partitions 
and the second one crashes
{color:#505f79}*THEN*{color} the first one should process duplicates of the 
messages that originally came to the second (at_least_once delivery)
h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
same group id{color} subscribed to the same topic with exactly two partitions 
with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}latest{color}.
{color:#505f79}*WHEN a*{color} messages were already present on both partitions 
and the second one crashes
{color:#505f79}*THEN*{color} the first one should {color:#0747a6}not{color} 
process duplicates of the messages that originally came to the second 
(at_least_once delivery)
h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
same group id{color} subscribed to the same topic with exactly two partitions 
with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}none{color}.
 {color:#505f79}*WHEN*{color} a messages were already present on both 
partitions and the second one crashes
 {color:#505f79}*THEN*{color} the first one should throw an exception

*Background:*

See parent task.

*Proposal:*

This should be the first part of the implementation, the second being adding 
and testing multiple security protocols.

  was:
*Acceptance Criteria:*

See attached test matrix plan.

Additional test (that require multiple Kafka consumers):
GIVEN two ConsumeKafkas with {color:#0747A6}different group ids{color} 
subscribed to the same topic
WHEN a message is published to the topic
THEN both of the ConsumeKafka processors should produce identical flowfiles

GIVEN two ConsumeKafkas with {color:#0747A6}the same group id{color} subscribed 
to the same topic
WHEN a message is published to the topic
THEN both of the ConsumeKafka processors should produce identical flowfiles

GIVEN two ConsumeKafkas with {color:#0747A6}the same group id{color} subscribed 
to the same topic with exactly two partitions with {color:#0747A6}Offset 
Reset{color} set to {color:#0747A6}earliest{color}.
WHEN a messages were already present on both partitions and the second one 
crashes
THEN the first one should process duplicates of the messages that originally 
came to the second (at_least_once delivery)

GIVEN two ConsumeKafkas with {color:#0747A6}the same group id{color} subscribed 
to the same topic with exactly two partitions with {color:#0747A6}Offset 
Reset{color} set to {color:#0747A6}latest{color}.
WHEN a messages were already present on both partitions and the second one 
crashes
THEN the first one should {color:#0747A6}not{color} process duplicates of the 
messages that originally came to the second (at_least_once delivery)

GIVEN two ConsumeKafkas with {color:#0747A6}the same group id{color} subscribed 
to the same topic with exactly two partitions with {color:#0747A6}Offset 
Reset{color} set to {color:#0747A6}none{color}.
WHEN a messages were already present on both partitions and the second one 
crashes
THEN the first one should throw an exception

*Background:*

See parent task.

*Proposal:*

This should be the first part of the implementation, the second being adding 
and testing multiple security protocols.


> Implement and test a simplified ConsumeKafka processor without security 
> protocols
> ---------------------------------------------------------------------------------
>
>                 Key: MINIFICPP-1373
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1373
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Sub-task
>    Affects Versions: 0.7.0
>            Reporter: Adam Hunyadi
>            Assignee: Adam Hunyadi
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: ConsumeKafka_test_matrix.pdf
>
>
> *Acceptance Criteria:*
> *{color:#de350b}See attached test matrix plan.{color}*
> Additional test (that require multiple Kafka consumers):
> h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with 
> {color:#0747a6}different group ids{color} subscribed to the same topic
>  {color:#505f79}*WHEN*{color} a message is published to the topic
>  {color:#505f79}*THEN*{color} both of the ConsumeKafka processors should 
> produce identical flowfiles
> h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
> same group id{color} subscribed to the same topic
> {color:#505f79}*WHEN*{color} a message is published to the topic
> {color:#505f79}*THEN*{color} both of the ConsumeKafka processors should 
> produce identical flowfiles
> h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
> same group id{color} subscribed to the same topic with exactly two partitions 
> with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}earliest{color}.
> {color:#505f79}*WHEN*{color} a messages were already present on both 
> partitions and the second one crashes
> {color:#505f79}*THEN*{color} the first one should process duplicates of the 
> messages that originally came to the second (at_least_once delivery)
> h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
> same group id{color} subscribed to the same topic with exactly two partitions 
> with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}latest{color}.
> {color:#505f79}*WHEN a*{color} messages were already present on both 
> partitions and the second one crashes
> {color:#505f79}*THEN*{color} the first one should {color:#0747a6}not{color} 
> process duplicates of the messages that originally came to the second 
> (at_least_once delivery)
> h6. {color:#505f79}*GIVEN*{color} two ConsumeKafkas with {color:#0747a6}the 
> same group id{color} subscribed to the same topic with exactly two partitions 
> with {color:#0747a6}Offset Reset{color} set to {color:#0747a6}none{color}.
>  {color:#505f79}*WHEN*{color} a messages were already present on both 
> partitions and the second one crashes
>  {color:#505f79}*THEN*{color} the first one should throw an exception
> *Background:*
> See parent task.
> *Proposal:*
> This should be the first part of the implementation, the second being adding 
> and testing multiple security protocols.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to