[FLINK-17946][python] fix the bug that the config option 'pipeline.jars' doesn't work.

[WeiZhong94]

What is the purpose of the change

This pull request fixes the bug that the config option 'pipeline.jars' doesn't work.

Brief change log

• Transfer the configuration of "pipeline.jars" and "pipeline.classpaths" from TableConfig to ExecEnv in every API that can execute job.

Verifying this change

This change is already covered by existing tests, such as test_table_environment_api.py.

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/Mesos, 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? (not applicable)

[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 c6d68db (Thu May 28 06:22:27 UTC 2020)

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:

• b975990 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

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

[dianfu]

@WeiZhong94 Thanks for the fix, just two minor comments:

• Should we also execute _before_execute() in sql_update?
• Could we also update the doc about pipeline.jars as it seems not correct?

[WeiZhong94]

@dianfu Thanks for your review! I have addressed your comments. It is unnecessary to execute _before_execute() in sql_update as it won't execute the pipeline really.

[dianfu]

@WeiZhong94 Thanks for the update. LGTM.

[dianfu]

The test failure is a known issue which is tracked in FLINK-17260. Merging...