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

Update and re-enable S3PlannerTest

    XMLWordPrintableJSON

Details

    • Test
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 3.4.0
    • None
    • None
    • ghx-label-14

    Description

      It looks like we don't run S3PlannerTest in our regular Jenkins jobs. When run against a HDFS mini-cluster, they are skipped because the TARGET_FILESYSTEM is not S3. On our S3 jobs, they don't run either because we skip all fe/ tests (most of them don't work against S3 / assume they are running on HDFS).

      A few things need to be fixed to get this working:

      • The test cases in S3PlannerTest need to be fixed
      • The Jenkins jobs that runs the S3 tests needs the ability to run specific fe/ tests (e.g. just the S3PlannerTest and to skip the rest)

      Attachments

        Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-8942 Set file format specific values for split sizes on non-block stores

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-8949 PlannerTest differences when running on S3 vs HDFS

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-5931 Don't synthesize block metadata in the catalog for S3/ADLS

          • Major - Major loss of function.
          • Closed

          Activity

            People

              stakiar Sahil Takiar
              stakiar Sahil Takiar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: