[jira] [Resolved] (IMPALA-1173) create-load-data.sh shouldn't try to do load-data.py --force when loading from a snapshot

["Joe McDonnell (Jira)" <ji...@apache.org>]

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

Joe McDonnell resolved IMPALA-1173.
-----------------------------------
    Resolution: Won't Fix

Dataload has gotten much faster, and it is rare to use snapshots to load data on a personal machine. If we decide to address deficiencies there, we'll open a new JIRA.

> create-load-data.sh shouldn't try to do load-data.py --force when loading from a snapshot
> -----------------------------------------------------------------------------------------
>
>                 Key: IMPALA-1173
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1173
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.0
>            Reporter: Daniel Hecht
>            Assignee: Joe McDonnell
>            Priority: Minor
>
> testdata/bin/create-load-data.sh first loads a snapshot.  Afterwards, it checks to make sure the loaded schema matches that in git.  If it doesn't match, it forces a reload through load-data.py.
> If the user supplied a snapshot file, then I think it would be better to fail when the schema mismatch is detected rather than falling back to the load_data.py --force path.  It seems more likely that the user would prefer to download an updated snapshot to resolve the situation.
> This has burned me a couple of times now when I've downloaded snapshots in the window between the schema update and when the new snapshot is ready.  Surprising (to me at least), the scripts went down the load_data.py --force path, which led to another problem (which Lenni as since fixed). But it would have been better if the script just told me that my snapshot is out of date to begin with.



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