You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2014/09/15 04:32:33 UTC

[jira] [Commented] (KAFKA-1611) Improve system test configuration

    [ https://issues.apache.org/jira/browse/KAFKA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133510#comment-14133510 ] 

Neha Narkhede commented on KAFKA-1611:
--------------------------------------

[~gwenshap] Thanks for the patch and apologize for the late review. We are trying to improve the management of the review backlog (see Reviewer thread on the mailing list) and will try our best to improve the review turnaround time and tracking. 

> Improve system test configuration
> ---------------------------------
>
>                 Key: KAFKA-1611
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1611
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Gwen Shapira
>            Assignee: Gwen Shapira
>             Fix For: 0.9.0
>
>         Attachments: KAFKA-1611.0.patch
>
>
> I'd like to make the config a bit more "out of the box" for the common case of local cluster. This will include:
> 1. Fix cluster_config.json of migration testsuite, it has hardcoded path that prevents it from working out of the box at all. 
> 2. Use JAVA_HOME environment variable if "default" is specified and if JAVA_HOME is defined. The current guessing method is a bit broken and using JAVA_HOME will allow devs to configure their default java dir without editing multiple cluster_config.json files in multiple places. 
> 3. (if feasible without too much headache): Configure remote hosts only for test packages that will not be skipped. This will reduce some overhead in the common use cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)