You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bahir.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/20 22:11:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16797607#comment-16797607 ] 

ASF GitHub Bot commented on BAHIR-200:
--------------------------------------

eskabetxe commented on pull request #49: [BAHIR-200] change test from docker to kudu-test-utils
URL: https://github.com/apache/bahir-flink/pull/49
 
 
   @lresende could you check
 
----------------------------------------------------------------
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:
users@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
>            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)