executor: Fix index join hash produces redundant rows for left outer anti semi join type (#52908)

[ti-chi-bot]

This is an automated cherry-pick of #52908

What problem does this PR solve?

Issue Number: close #52902

Problem Summary:
In IndexHashJoin inner work, we use join type to check if redundant matched rows should be appended to JoinResult. However, only semi and leftOuterSemi is recongnized:

tidb/pkg/executor/index_lookup_hash_join.go

Lines 739 to 752 in 8ba1fa4

	isSemiJoin := joinType == plannercore.SemiJoin || joinType == plannercore.LeftOuterSemiJoin
	for ; matchedOuterEntry != nil; matchedOuterEntry = matchedOuterEntry.next {
	ptr := matchedOuterEntry.ptr
	outerRow := task.outerResult.GetRow(ptr)
	ok, err := codec.EqualChunkRow(iw.ctx.GetSessionVars().StmtCtx.TypeCtx(), innerRow, iw.hashTypes, iw.hashCols, outerRow, iw.outerCtx.hashTypes, iw.outerCtx.hashCols)
	if err != nil {
	return nil, nil, err
	}
	if !ok || (task.outerRowStatus[ptr.ChkIdx][ptr.RowIdx] == outerRowMatched && isSemiJoin) {
	continue
	}
	matchedRows = append(matchedRows, outerRow)
	matchedRowPtr = append(matchedRowPtr, chunk.RowPtr{ChkIdx: ptr.ChkIdx, RowIdx: ptr.RowIdx})
	}

While anti-semi join doesn't care matched rows, left outer anti semi will append joined rows, thus caused the problem.

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[xzhangxian1008]

LGTM

[ti-chi-bot]

@xzhangxian1008: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

LGTM

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[windtalker]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SeaRise, windtalker, xzhangxian1008

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [windtalker]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-28 03:18:01.107789912 +0000 UTC m=+154434.864925481: ☑️ agreed by windtalker.
• 2024-04-28 04:06:36.598715533 +0000 UTC m=+157350.355851103: ☑️ agreed by SeaRise.