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

ASF GitHub Bot commented on KAFKA-8200:
---------------------------------------

pkleindl commented on pull request #6556: KAFKA-8200: added Iterator methods 
for output to TopologyTestDriver
URL: https://github.com/apache/kafka/pull/6556
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> TopologyTestDriver should offer an iterable signature of readOutput
> -------------------------------------------------------------------
>
>                 Key: KAFKA-8200
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8200
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Michael Drogalis
>            Assignee: Patrik Kleindl
>            Priority: Minor
>              Labels: needs-kip
>
> When using the TopologyTestDriver, one examines the output on a topic with 
> the readOutput method. This method returns one record at a time, until no 
> more records can be found, at which point in returns null.
> Many times, the usage pattern around readOutput will involve writing a loop 
> to extract a number of records from the topic, building up a list of records, 
> until it returns null.
> It would be helpful to offer an iterable signature of readOutput, which 
> returns either an iterator or list over the records that are currently 
> available in the topic. This would effectively remove the loop that a user 
> needs to write for him/herself each time.
> Such a signature might look like:
> {code:java}
> public Iterable<ProducerRecord<byte[],byte[]>> readOutput(java.lang.String 
> topic);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to