You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bahir.apache.org by "Luciano Resende (JIRA)" <ji...@apache.org> on 2019/05/26 00:48:00 UTC

[jira] [Resolved] (BAHIR-200) change from docker tests to kudu-test-utils

     [ https://issues.apache.org/jira/browse/BAHIR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luciano Resende resolved BAHIR-200.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Flink-Next

> 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
>             Fix For: Flink-Next
>
>
> 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)