[FLINK-22781][table-planner-blink] Fix bug that when implements the LookupFunction In SQL that indirect extends (Async)TableFunction, throw exception

[adiaixin]

…ookupFunction In SQL that indirect extends (Async)TableFunction, throw exception

What is the purpose of the change

when implements the LookupFunction In SQL that indirect extends (Async)TableFunction, we extract the output type class use ExtractionUtils#extractSimpleGeneric, this method will return empty when dealing with indirect extended subclasses. We need to fix this bug.

Brief change log

• change method ExtractionUtils#extractSimpleGeneric, traverse all the super classes to the base class until find the generic parameter in pos has real class type.

Verifying this change

(Please pick either of the following options)

This change added tests and can be verified as follows:

• Added a unit Test which verified the static method result. （org.apache.flink.table.utils.ExtractionUtilsTest）

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
• If yes, how is the feature documented? no

[flinkbot]

CI report:

• d8153a4 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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

[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 d8153a4 (Fri Feb 11 08:01:54 UTC 2022)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{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

[adiaixin]

@flinkbot run azure

[adiaixin]

@twalthr
hi, could you review this pr when you are free ?