[
https://issues.apache.org/jira/browse/IMPALA-9331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313294#comment-17313294
]
ASF subversion and git services commented on IMPALA-9331:
---------------------------------------------------------
Commit 559f6044bed1c0bcfe0312b2eb2c349450628e76 in impala's branch
refs/heads/master from Laszlo Gaal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=559f604 ]
IMPALA-9331: Add symptom for dataload failing on schema mismatch
Streamline triaging a bit. When this fails, it does so in a specific
location, and until now you had to scan the build log to find the
problem. This JUnitXML symptom should make this failure mode obvious.
Tested by running an S3 build on private infrastructure with a knowingly
mismatched data snapshot.
Change-Id: I2fa193740a2764fdda799d6a9cc64f89cab64aba
Reviewed-on: http://gerrit.cloudera.org:8080/17242
Reviewed-by: Laszlo Gaal <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
