Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-4366 Aggregation Improvement
  3. SPARK-10100

Eliminate hash table lookup if there is no grouping key in aggregation.

Rank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.5.0
    • 1.5.0
    • SQL
    • None

    Description

      Update: The title of this jira has been changed to "Eliminate hash table lookup if there is no grouping key in aggregation.". For the Max and Min expressions, we can revisit them later if we find a better way to improve the performance and open a new jira.

      The original title of this JIRA is "AggregateFunction2's Max is slower than AggregateExpression1's MaxFunction". Below is the original description:
      Looks like Max (probably Min) implemented based on AggregateFunction2 is slower than the old MaxFunction.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rxin Reynold Xin
            yhuai Yin Huai
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment