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 2018/04/23 17:55:00 UTC

[jira] [Resolved] (IMPALA-6898) Dataload from scratch loads Kudu tables twice

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

Joe McDonnell resolved IMPALA-6898.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.13.0
                   Impala 3.0

> Dataload from scratch loads Kudu tables twice
> ---------------------------------------------
>
>                 Key: IMPALA-6898
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6898
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 3.1.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 3.0, Impala 2.13.0
>
>
> When doing a full dataload, testdata/bin/create-load-data.sh runs bin/load-data.py for functional/exhaustive, tpch/core, and tpcds/core. Then, in a separate phase, it loads functional and TPC-H for Kudu.
> For a full dataload, this second phase is not necessary, because functional/exhaustive and tpch/core already include Kudu versions of these tables.
> For a snapshot dataload, this second phase is still necessary as the snapshot does not include Kudu.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)