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

Posted to issues@impala.apache.org by "Jim Apple (JIRA)" <ji...@apache.org> on 2017/08/11 07:11:00 UTC

[jira] [Resolved] (IMPALA-4407) Incorporate impala-setup repo into main Impala repo

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

Jim Apple resolved IMPALA-4407.
-------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0

https://github.com/apache/incubator-impala/commit/d5cefe07c931a0d3bf02bca97bbba05400d91a48

> Incorporate impala-setup repo into main Impala repo
> ---------------------------------------------------
>
>                 Key: IMPALA-4407
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4407
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 2.8.0
>            Reporter: Jim Apple
>            Assignee: Jim Apple
>             Fix For: Impala 2.10.0
>
>
> https://github.com/awleblang/impala-setup should be part of the main Impala repo, so changes made in Impala get reflected  in setup, and bugs against impala-setup make sense against Impala, and so on.
> This
> https://github.com/awleblang/impala-setup/issues/9
> caused
> https://issues.cloudera.org/browse/IMPALA-4404



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)