Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encapsulate EmbeddedSingleNodeKafkaCluster in a seperately-available maven/gradle/sbt dep #26

Open
peoplemerge opened this issue Nov 10, 2017 · 7 comments

Comments

Projects
None yet
5 participants
@peoplemerge
Copy link

commented Nov 10, 2017

As discussed in this thread https://groups.google.com/forum/#!topic/confluent-platform/_pJ1g9g1woY

It would be great if I could just include EmbeddedSingleNodeKafkaCluster and it's deps in test scope to easily run integration tests. It seems like right now there is a lot of cut & paste programming happening out there.

@ryan-barker-zefr

This comment has been minimized.

Copy link

commented Apr 23, 2018

This is a really big deficiency for our team. Not having an artifact to make testing easier seems like a big deal to me.

Is the current acceptable use to copy and paste?

@guozhangwang

This comment has been minimized.

Copy link
Member

commented Apr 23, 2018

We are indeed working on getting a core-test-utils artifact which will include some mocked broker module for users to write integration tests easier. That is on our ongoing roadmap.

For now please bare with us and use the copy-paste approach.

@cricket007

This comment has been minimized.

Copy link

commented Feb 14, 2019

Is there a JIRA to watch for this? I notice that at least connect and streams have the a similar EmbeddedKafkaBroker class in their unit tests.

@mjsax

This comment has been minimized.

@cricket007

This comment has been minimized.

Copy link

commented Feb 14, 2019

Thanks!

In the meantime, we've been using a combination of the testcontainers or junit-kafka projects

@ryan-barker-zefr

This comment has been minimized.

Copy link

commented Feb 14, 2019

We have made some progress on our side. We are looking into making an open source version of this but honestly we'd prefer to provide the code that we have done and have confluent maintain it.

@cricket007

This comment has been minimized.

Copy link

commented Feb 14, 2019

The embedded cluster would be mantained in the Apache Kafka repo, not just by Confluent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.