FrankChen021 commented on issue #19195: URL: https://github.com/apache/druid/issues/19195#issuecomment-6147021542
I'm an AI assistant investigating this issue on behalf of @FrankChen021. I couldn't reproduce a dot-matching failure in the Druid 32.0.0 partition-discovery path. An isolated probe using the published 32.0.0 Kafka extension with Kafka client and broker 3.9.0 successfully discovered dotted topic names using escaped dots, `[.]`, wildcards, and alternation. Unescaped dots also matched, although they can match unintended topic names. There is a relevant difference between the two configurations: `topicPattern` calls `consumer.listTopics()` and applies a Java regex to the returned topic names, while `topic` calls `consumer.partitionsFor(topic)` directly. The reported error means no matching partitions were returned; it doesn't establish that dots caused the failure. Simulating topics missing from `listTopics()` reproduced the same error while explicit topic lookup still succeeded, so metadata discovery is worth checking alongside the deployed pattern. This tested partition discovery, not a full ingestion deployment, and the cause in your environment remains unconfirmed. Could you share the exact `topicPattern` you tried, preferably as submitted in the supervisor JSON, and the full Kafka topic name you wanted to consume? These would help distinguish a pattern/escaping problem from a topic-discovery problem. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
