[jira] [Resolved] (NIFI-6836) ConsumeKafkaRecord_1_0 reads data from first 100 topics

["Pierre Villard (Jira)" <ji...@apache.org>]

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

Pierre Villard resolved NIFI-6836.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> ConsumeKafkaRecord_1_0 reads data from first 100 topics
> -------------------------------------------------------
>
>                 Key: NIFI-6836
>                 URL: https://issues.apache.org/jira/browse/NIFI-6836
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.9.2
>            Reporter: Bartłomiej Tartanus
>            Priority: Major
>              Labels: easyfix
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> ConsumeKafkaRecord_1_0 reads data from first 100 topics and ignores the rest. This bug is caused by this line:
>  [https://github.com/apache/nifi/blob/45ebeba846cf257c0dd27669c25e244208758fb9/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-1-0-processors/src/main/java/org/apache/nifi/processors/kafka/pubsub/ConsumeKafkaRecord_1_0.java#L316]
> This might be easily fixed by removing {{,100}} but I assume someone put this limit for a reason. If this limit is needed then some mention in documentation should be added. Also a validator that checks if number of topics is not greater than 100.
> I can prepare merge request if we agree what to do with this issue.
>  
> Current workaround is to add another ConsumeKafkaRecord_1_0 processor and split the list in parts, each containing at most 100 topics.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)