Laszlo Gaal created IMPALA-9331:
-----------------------------------
Summary: Generate JUnitXML symptom to detect failed dataload due
to schema mismatch
Key: IMPALA-9331
URL: https://issues.apache.org/jira/browse/IMPALA-9331
Project: IMPALA
Issue Type: Improvement
Components: Infrastructure
Affects Versions: Impala 3.4.0
Reporter: Laszlo Gaal
Impala test runs can still load the test database from a snapshot instead of
generating it on the fly.
This capability has a specific failure mode when the dataload code detects that
the database structure expected by the current state of the code is different
from the structure represented in the data snapshot, and it decides that the
problem cannot be fixed by switching to test data generation on the fly.
Triaging this failure mode should be made easier (or possibly automatic) by
identifying the specific error output and generating a unique JunitXML symptom
from it, which should prevent people from having to dig through the build log
to discover the specific error message:
{code}
ERROR in ...../Impala/testdata/bin/create-load-data.sh at line 134: A schema
change has been detected in the
metadata, but it cannot be loaded on isilon, s3 or local and the
target file system is s3. Exiting.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
