Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.12.0
    • Component/s: Diagnosability
    • Labels:
      None

      Description

      In various situations it would have been useful to me to glance at the operator plan before we break it into tasks and apply join, total order sort, etc optimizations.

      I've added this as an options to explain. "Explain logical <QUERY>" will output the full operator tree (not the stage plans, tasks, AST etc).

      Again, I don't think this has to even be documented for users, but might be useful to developers.

      1. HIVE-4812.1.patch
        42 kB
        Gunther Hagleitner
      2. HIVE-4812.2.patch
        46 kB
        Gunther Hagleitner
      3. HIVE-4812.3.patch
        46 kB
        Gunther Hagleitner

        Issue Links

          Activity

          Gunther Hagleitner created issue -
          Gunther Hagleitner made changes -
          Field Original Value New Value
          Link This issue blocks HIVE-4660 [ HIVE-4660 ]
          Gunther Hagleitner made changes -
          Attachment HIVE-4812.1.patch [ 12590577 ]
          Gunther Hagleitner made changes -
          Attachment HIVE-4812.2.patch [ 12590711 ]
          Gunther Hagleitner made changes -
          Attachment HIVE-4812.3.patch [ 12591108 ]
          Gunther Hagleitner made changes -
          Link This issue depends upon HIVE-4811 [ HIVE-4811 ]
          Gunther Hagleitner made changes -
          Summary Explain plan for physical operators Logical explain plan
          Gunther Hagleitner made changes -
          Description In various situations it would have been useful to me to glance at the operator plan before we break it into tasks and apply join, total order sort, etc optimizations.

          I've added this as an options to explain. "Explain physical <QUERY>" will output the full operator tree (not the stage plans, tasks, AST etc).

          Again, I don't think this has to even be documented for users, but might be useful to developers.
          In various situations it would have been useful to me to glance at the operator plan before we break it into tasks and apply join, total order sort, etc optimizations.

          I've added this as an options to explain. "Explain logical <QUERY>" will output the full operator tree (not the stage plans, tasks, AST etc).

          Again, I don't think this has to even be documented for users, but might be useful to developers.
          Navis made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 0.12.0 [ 12324312 ]
          Resolution Fixed [ 1 ]
          Navis made changes -
          Component/s Diagnosability [ 12314270 ]
          Ashutosh Chauhan made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Gunther Hagleitner
              Reporter:
              Gunther Hagleitner
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development