Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-16629

Wrong calculation of replies count for queries with partition pruning and enabled parallelism

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 2.13
    • sql
    • Fixed wrong calculation of replies count for queries with partition pruning and enabled parallelism
    • Release Notes Required

    Description

      Currently a simple query is freezing forever if query parallelism is enabled and partition pruning extracts more than one partition. This caused by wrong replies count estimation made on a reducer node.

      The problematic query looks like this: select * from t where aff_key in ('a', 'b', 'c').

      Please note that field aff_key should be an affinity key and be a part of the compound PK.

      Attachments

        Issue Links

        Activity

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

          People

            jooger Iurii Gerzhedovich
            jooger Iurii Gerzhedovich
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

              Slack

                Issue deployment