Details
-
Bug
-
Status: To Do
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
A bug in Spring and/or kafka forced us to move the KafkaComponent from a shared component via the Spring Test configuration profile into a component that was spun up and down per test-case as of METRON-1004.
This puts us in an awkward spot where we're neither matching the pattern in the rest of the (non-spring-oriented portion of the) project nor are we really matching the intention of Spring. As such, due to the zookeeper component being AutoWired and a member variable, we can't mix and match Junit @AfterClass and @BeforeClass semantics that we use elsewhere in the project to share components across testcases. This is muddled. We should upgrade Spring to the version with the fix to the intermittent error (see https://github.com/spring-projects/spring-kafka/issues/194) and revert the test to using AutoWired KafkaComponent that is setup in the spring test config.