As @guozhangwang pointed out, the error does not occur until we go to build the topology and the duplicate topic name is detected and at that point, the error is thrown.
I can update with the `try-fail-catch` pattern, but have we established this as a convention of unit tests vs using the `@Test(expected=...)` approach? [ Full content available at: https://github.com/apache/kafka/pull/5709 ] This message was relayed via gitbox.apache.org for [email protected]
