Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-9331

Generate JUnitXML symptom to detect failed dataload due to schema mismatch

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 3.4.0
    • Impala 4.0.0
    • Infrastructure
    • None

    Description

      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:

      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.
      

      Attachments

        Activity

          People

            laszlog Laszlo Gaal
            laszlog Laszlo Gaal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: