[
https://issues.apache.org/jira/browse/BAHIR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843549#comment-16843549
]
ASF GitHub Bot commented on BAHIR-200:
--------------------------------------
lresende commented on issue #49: [BAHIR-200] change test from docker to
kudu-test-utils
URL: https://github.com/apache/bahir-flink/pull/49#issuecomment-493792861
Suggestion for the future, once a different PR get's merged into master,
update your master, rebase the pr branch to master, and push (--force). to the
repo... this avoids increasing the number of commits showing in this PR and
also makes the "changed files" exactly what is being added to the PR.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> change from docker tests to kudu-test-utils
> -------------------------------------------
>
> Key: BAHIR-200
> URL: https://issues.apache.org/jira/browse/BAHIR-200
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Reporter: Joao Boto
> Assignee: Joao Boto
> Priority: Major
>
> As of version 1.9.0, Kudu ships with an experimental feature called the
> binary test JAR. This feature gives people who want to test against Kudu the
> capability to start a Kudu "mini cluster" from Java or another JVM-based
> language without having to first build Kudu locally
>
> https://kudu.apache.org/docs/developing.html#_jvm_based_integration_testing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
