Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-17626 Query reoptimization using cached runtime statistics
  3. HIVE-18238

Driver execution may not have configuration changing sideeffects

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0
    • Logical Optimizer
    • None

    Description

      Driver executes sql statements which use "hiveconf" settings;
      but the Driver itself may not change the configuration...

      I've found an example; which shows how hazardous this is...

      set hive.mapred.mode=strict;
      select "${hiveconf:hive.mapred.mode}";
      create table t (a int);
      analyze table t compute statistics;
      select "${hiveconf:hive.mapred.mode}";
      

      currently; the last select returns nonstrict because of this

      Attachments

        1. HIVE-18238.01wip01.patch
          25 kB
          Zoltan Haindrich
        2. HIVE-18238.02.patch
          28 kB
          Zoltan Haindrich
        3. HIVE-18238.03.patch
          46 kB
          Zoltan Haindrich
        4. HIVE-18238.04.patch
          51 kB
          Zoltan Haindrich
        5. HIVE-18238.04wip01.patch
          56 kB
          Zoltan Haindrich
        6. HIVE-18238.07.patch
          62 kB
          Zoltan Haindrich
        7. HIVE-18238.08.patch
          58 kB
          Zoltan Haindrich
        8. HIVE-18238.09.patch
          58 kB
          Zoltan Haindrich
        9. HIVE-18238.10.patch
          58 kB
          Zoltan Haindrich
        10. HIVE-18238.11.patch
          55 kB
          Zoltan Haindrich

        Issue Links

          Activity

            People

              kgyrtkirk Zoltan Haindrich
              kgyrtkirk Zoltan Haindrich
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: