[FLINK-26016][hive] Fix FileSystemLookupFunction can't build correct cache when reading columnar storage table

[hackergin]

What is the purpose of the change

*Fix lookup join bug when reading hive columnar storage tables. *

Brief change log

• When building the cache, generate cache key after copy the RowData from columnar RowData in case of different key reference the same memory

Verifying this change

This change added tests and can be verified as follows:

Unit tests

• Add test in [HiveLookupJoinITCase.java] to test lookup join with columnar table and make sure there is enough records to make sure the ParquetVectorizedInputFormat will read at least two batch to reproduce the error

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit fcaabbf (Tue Feb 15 10:49:52 UTC 2022)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!
• This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• 1112c01 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[luoyuxia]

@hackergin Thanks for contribution. LGTM.
@wuchong @JingsongLi Do you have time to help review&merge?

[JingsongLi]

Looks good to me! Thanks for the contribution!

[JingsongLi]

@hackergin can you create pr for release-1.14?

[hackergin]

@JingsongLi sure.

[hackergin]

@JingsongLi I submitted the pr for release-1.14 #18857