[
https://issues.apache.org/jira/browse/STORM-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268960#comment-15268960
]
ASF GitHub Bot commented on STORM-1736:
---------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1376#issuecomment-216579561
@HeartSaVioR @abhishekagarwal87 this issues happens with Kafka 0.10 branch.
Yes it does break test compatability with 0.8.x . Keep in mind that
KafkaConfig is an internal kafka class that we use to start a in-process kafka
broker. We shouldn't be calling it as breaking comptability with client api.
Also this change will work with Kafka 0.9.x on wards
> Change KafkaTestBroker.buildKafkaConfig to new KafkaConfig api.
> ---------------------------------------------------------------
>
> Key: STORM-1736
> URL: https://issues.apache.org/jira/browse/STORM-1736
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Sriharsha Chintalapani
> Assignee: Sriharsha Chintalapani
>
> 1.x-branch failing with following error
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile
> (default-testCompile) on project storm-kafka: Compilation failure
> [ERROR]
> /Users/harsha/code/harshach/incubator-storm/external/storm-kafka/src/test/org/apache/storm/kafka/KafkaTestBroker.java:[70,16]
> constructor KafkaConfig in class kafka.server.KafkaConfig cannot be applied
> to given types;
> [ERROR] required: java.util.Map<?,?>,boolean
> [ERROR] found: java.util.Properties
> [ERROR] reason: actual and formal argument lists differ in length
> [ERROR] -> [Help 1]
> [ERROR]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
