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

Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/12/24 01:25:00 UTC

[jira] [Resolved] (IMPALA-4398) Impala-Kudu upgrade test

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

Joe McDonnell resolved IMPALA-4398.
-----------------------------------
    Fix Version/s: Not Applicable
       Resolution: Won't Fix

> Impala-Kudu upgrade test
> ------------------------
>
>                 Key: IMPALA-4398
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4398
>             Project: IMPALA
>          Issue Type: Task
>          Components: Infrastructure
>    Affects Versions: Kudu_Impala
>            Reporter: Matthew Jacobs
>            Priority: Major
>              Labels: kudu, test, usability
>             Fix For: Not Applicable
>
>
> Given all of the changes to Kudu tables in 2.8. We should have tests that ensure that Kudu tables created before Impala 2.8 will continue to work after.
> We should at least test both internal and external tables can be read after an upgrade.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)