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

Improve always-true min/max filter handling in coordinator

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

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 4.0.0
    • None
    • None
    • ghx-label-2

    Description

      Currently, when a just arriving min/max filter is the last one to arrive or is always true, the coordinator disables the corresponding filter
      representation by setting it to Always True. This makes it impossible to differentiate a true AlwaysTrue filter (say, set in the
      hash join building step) from the one being disabled.

      A better handling is needed in this area.

      Attachments

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

          People

            sql_forever Qifan Chen
            sql_forever Qifan Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment